Hi Kapil,
Kapil Hari Paranjape <ka...@imsc.res.in> writes:
> It is possible that most users will not uninstall acpid and acpi-support
> like I did. However, given that the sleep handling of that package will
> interfere with the parallel handling by systemd, most online help
> instructions suggest that users _disable_ ACPI_SLEEP and ACPI_SUSPEND from
> /etc/default/acpi-support. At this point, the sleep key will again stop
> working for them (at least on this laptop)!
I purged acpid and acpi-support{,-base} from my ThinkPad X200, then
restarted systemd-logind.service. When I press the suspend key, logind
will properly recognize that and suspend the machine:
$ journalctl -f -u systemd-logind.service
Jan 26 11:19:28 x200 systemd-logind[11478]: Suspend key pressed.
Jan 26 11:19:28 x200 systemd-logind[11478]: Suspending...
Jan 26 11:19:36 x200 systemd-logind[11478]: Operation finished.
Jan 26 11:19:36 x200 systemd-logind[11478]: New session c2 of user michael.
Jan 26 11:19:36 x200 systemd-logind[11478]: Removed session c2.
So, I conclude this is not a bug in (our packaging of) systemd/logind,
but rather most likely a configuration issue somewhere on your
machine. Perhaps there is yet another program that might grab/react to
this button? Also, did you try cold-booting your machine? On mine, after
you press the suspend key, the firmware is confused if no suspend
actually happens, i.e. further keypresses will not generate an event.
--
Best regards,
Michael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
