<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - logind (version 204-6) fails to catch suspend key (Acer Aspire One D250)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74269">74269</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>logind (version 204-6) fails to catch suspend key (Acer Aspire One D250)
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>kapil@debian.org
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>Hello,
(Please see bugs.debian.org/736389 for the earlier report.)
As mentioned in the report above logind (systemd version 204-6)
does not receive the "sleep key" Fn+F4. However, this key does
generate the correct keycode (checked with showkey on the console and
Xev). The journal also records that logind is set up to watch for the
key. The udev info also records that it has /dev/input/event[n] with tag
"power-switch".
The system (Acer Aspire One D250) is running Debian jessie (Linux
3.12-1-amd64 #1 SMP Debian 3.12.6-2 (2013-12-29) x86_64 GNU/Linux). It
is a barebones system installed via debootstrap and only contains basic
text-mode utilities along with systemd. I can debug further if given
indications on how to do this.
Before using systemd, I was using the acpid mechanism to trigger an
event handler. So acpid *was* seeing the key.
As indicated in the 30/01/2014 mailing by me, I do not know where to
look between the kernel and systemd/logind to find out which process is
preventing the key event being sent to logind.
Any help will be appreciated.
Regards,
Kapil.
--</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>