Bug#794744: systemd-logind: Lid closed event does not suspend

[Antonio Terceiro]

On Sun, 20 Sep 2015 20:41:26 -0300 Antonio Terceiro <terceiro at debian.org> wrote:
> I am experiencing exactly the same with the latest systemd on unstable;
> `systemctl suspend` works, but closing the lid does not suspend (at all).

after rebooting with systemd.log_level=debug, the journal now says:

Set 20 20:50:26 homer systemd-logind[619]: Lid closed.
Set 20 20:50:26 homer systemd-logind[619]: System is docked.
Set 20 20:50:26 homer systemd-logind[619]: Refusing operation, as it is turned off.
Set 20 20:50:26 homer systemd-logind[619]: System is docked.
Set 20 20:50:26 homer systemd-logind[619]: Refusing operation, as it is turned off.
Set 20 20:50:26 homer systemd[1]: systemd-logind.service: Got notification message from PID 619 (WATCHDOG=1)
Set 20 20:51:00 homer systemd-logind[619]: Lid opened.
Set 20 20:51:00 homer systemd[1]: systemd-logind.service: Got notification message from PID 619 (WATCHDOG=1)

the laptop is *not* docked, why would systemd think it is?

I was able to workaround this by adding `HandleLidSwitchDocked=suspend`
to /etc/systemd/logind.conf and restarting systemd-logind so that
closing the lid does suspend, but still systemd is incorrectly assuming
the system is docked when it isn't.

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150920/960dd0b8/attachment-0002.sig>