<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - ACPI _LID usage model change"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100923#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - ACPI _LID usage model change"
href="https://bugs.freedesktop.org/show_bug.cgi?id=100923">bug 100923</a>
from <span class="vcard"><a class="email" href="mailto:lv.zheng@intel.com" title="Lv Zheng <lv.zheng@intel.com>"> <span class="fn">Lv Zheng</span></a>
</span></b>
<pre>It's not simply a regression.
if you check the linked bugs.
You'll see there are buggy AML tables (buggy from lid notifiers' point of view,
but not from Windows compliance's point of view).
For that platforms, user actually should specify "button.lid_init_state=open"
to appeal systemd in order not to enter a suspend/resume cycle. And
"button.lid_init_state=close" to appeal x.org to light on correct monitors.
The 2 options are entirely mutual exclusive.
So the unexpected usage models of lid control method device must make changes.
And this report is meant to notify the desktop developers to change.
Thanks
Lv</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>