[systemd-devel] logind: lid switch action not executed on small open/close delays

[Alad Wenter]

On my Thinkpad X61 (lspci -v: http://pastie.org/9831762) running Arch 
Linux and i3wm, I use systemd-logind to suspend on lid close (without 
front-ends like upower, just xss-lock to run Xscreensaver).

It works nicely, except when closing the lid shortly after it was 
opened. The laptop does then not suspend; I haven't made exact 
measurements, but it's 10+ seconds. Using systemctl suspend (or the 
suspend special keys) does work as intended.

systemd --version

systemd 218
+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP 
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS 
+KMOD +IDN

dmesg log after suspending: http://pastie.org/9831761

journalctl -u systemd-logind

Jan 14 12:35:05 thinkpad systemd-logind[330]: Suspend key pressed.
Jan 14 12:35:05 thinkpad systemd-logind[330]: Suspending...
Jan 14 12:35:19 thinkpad systemd-logind[330]: Operation finished.
Jan 14 12:35:21 thinkpad systemd-logind[330]: Suspend key pressed.
Jan 14 12:35:21 thinkpad systemd-logind[330]: Suspending...
Jan 14 12:35:31 thinkpad systemd-logind[330]: Operation finished.
Jan 14 12:38:47 thinkpad systemd-logind[330]: Lid closed.
Jan 14 12:38:47 thinkpad systemd-logind[330]: Suspending...
Jan 14 12:38:55 thinkpad systemd-logind[330]: Lid opened.
Jan 14 12:38:55 thinkpad systemd-logind[330]: Operation finished.
Jan 14 12:38:56 thinkpad systemd-logind[330]: Lid closed.
Jan 14 12:39:05 thinkpad systemd-logind[330]: Lid opened.
Jan 14 12:39:09 thinkpad systemd-logind[330]: Lid closed.
Jan 14 12:39:18 thinkpad systemd-logind[330]: Lid opened.

So it seems the lid switch is recognized, but that's it. I don't think 
xss-lock is related as it's the same without it running.

PS: This may sound like an artificial use-case, but I'm on the move 
quite often (and am used to suspending this way), so I'd like to avoid 
my laptop still runs while in my bag...

Regards,

Alad