Bug#794744: systemd-logind: Lid closed event does not suspend
biebl at debian.org
Tue Oct 10 15:34:50 BST 2017
Control: tags -1 + moreinfo
On Thu, 06 Aug 2015 18:17:08 +1000 Brian May <bam at debian.org> wrote:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: important
> File: systemd-logind
> 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: Lid closed.
> Aug 6 15:20:47 prune systemd-logind: Lid opened.
> Occassionally the system does suspend, and I get the following logged:
> Aug 5 17:20:12 prune systemd-logind: Lid closed.
> Aug 5 17:20:12 prune systemd-logind: Suspending...
> Aug 5 17:26:04 prune systemd-logind: Lid opened.
> Aug 5 17:26:04 prune systemd-logind: 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.
> Curiously this problem only started as of last week. I asked about this
> on the local mailing list, but only got responses from anti-systemd
> people :-(.
> This type of problem can damage hardware if you put your computer away
> in your bag without realizing it didn't suspend and it overheats - this
> is what happened with me the first time it happened, but I think I
> caught it in time before it got too hot.
Is this problem still reproducible with a recent version of 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...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers