Hi Kapil, Kapil Hari Paranjape <ka...@imsc.res.in> writes: > On Sun, 26 Jan 2014, Michael Stapelberg wrote: >> $ 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... > > I did not ever get this in the journal. > > In fact, to test the setup, I did a "debootstrap" install of jessie, > followed by installing systemd-sysv, the kernel and kbd. (In other > words, a "bare-bones" install!) > > The "showkey" command still recognises the key as giving code "142" but > suspend does not work. > > I do not know where the problem lies. Perhaps systemd is relying on the > event driver for the specific key and not the keyboard driver to > generate the specific code (this is just a guess since I don't know much > about this). > > I can investigate some more if you let me know what you want > investigated. Can you please provide the output of the following command?
for dev in /dev/input/event* do udevadm info -q all -n $dev done What you should see in there is a line saying TAGS=:power-switch:, which will make logind listen to that input device for system button events. You should also see messages stating “Watching system buttons on /dev/input/event3 (Power Button)” in the journal, emitted by logind. Can you append the output of journalctl -u systemd-logind.service -b please? In case this is not enough of a hint to debug and fix this, it’d also be good to provide a full strace output of logind (overwrite the ExecStart line to wrap logind in strace). -- 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
