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

[Michael Biebl]

Hi Brian,

Am 06.08.2015 um 10:17 schrieb Brian May:
> When closing the lid, system doesn't suspend, all I get is the following
> logged in auth.log:
> 
> Aug  6 15:20:36 prune systemd-logind[571]: Lid closed.
> Aug  6 15:20:47 prune systemd-logind[571]: Lid opened.
> 
> Occassionally the system does suspend, and I get the following logged:
> 
> Aug  5 17:20:12 prune systemd-logind[571]: Lid closed.
> Aug  5 17:20:12 prune systemd-logind[571]: Suspending...
> Aug  5 17:26:04 prune systemd-logind[571]: Lid opened.
> Aug  5 17:26:04 prune systemd-logind[571]: Operation finished.
> 
> The following command always succeeds in suspending immediately:
> 
> systemctl suspend
> 
> Presumably something is happening in systemd-logind to cancel the
> suspend, but it would be nice if it could log what that was.


Do you use an external monitor? If logind detects an external monitor,
it suppresses any suspend requests.

It sounds, like this might be another case of
https://github.com/systemd/systemd/issues/451

I.e. the kernel reports "unknown" status for the DRM devices after the
first suspend.







-- 
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/20150806/0b35ae5a/attachment-0002.sig>