<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Unintended suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102959">bug 102959</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTOURBUG
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Unintended suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102959#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - Unintended suspend"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102959">bug 102959</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>(In reply to Paviluf from <a href="show_bug.cgi?id=102959#c2">comment #2</a>)
<span class="quote">> (In reply to Peter Hutterer from <a href="show_bug.cgi?id=102959#c1">comment #1</a>)
> > libinput doesn't do anything with suspend, the only thing it does is that it
> > disables the touchpad when a lid switch event is received. see
> > <a href="http://who-t.blogspot.com/2017/02/libinput-and-lid-switch-events.html">http://who-t.blogspot.com/2017/02/libinput-and-lid-switch-events.html</a> for an
> > explanation.
>
> Suspend is triggered (by systemd it seem) because libinput detect a lid
> event in the first place, right ?</span >
no. systemd and libinput simply listen to the same kernel device. The switch
event is delivered to both, each handle it in their own way. Whether libinput
(or anything else) is around doesn't matter for this particular bug.
even with WRITE_OPEN libinput *never* writes a lid close event, those always
come from the hardware.
<span class="quote">> > What does evemu-record on the device show in this case? Does it show an open
> > + close event?
>
> It will be hard to know since it only happened once in 10 days since I test
> the John Lewis firmware.</span >
right. In that case I'll close this bug here because the best we could do (if
the firmware is indeed confirmed to be broken) is the WRITE_OPEN approach
outlined above. If the lid state doesn't match the hardware state that is
either a kernel or ACPI bug. If the lid state matches but the suspend/resume
behaviour does not match, then that's a systemd bug.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>