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

[Michael Biebl]

Am 21.09.2015 um 01:59 schrieb 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?
> 

See
https://github.com/systemd/systemd/blob/master/src/login/logind-button.c#L269
and
https://github.com/systemd/systemd/blob/master/src/login/logind-core.c#L453

Either the the drm subsystem reports an external display or you have a
sw_dock switch which reports the system as docked.

Can you attach a debugger to find out what is the case and if this
either a kernel bug (reporting incorrect state) or a bug in systemd.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150921/de3339c9/attachment-0002.sig>