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

Michael Biebl writes: > Is this problem still reproducible with a recent version of systemd? Sorry, I can't even remember making this report now. Stretch seems fine. Please close it. -- Brian May

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

Control: tags -1 + moreinfo Hi Brian On Thu, 06 Aug 2015 18:17:08 +1000 Brian May 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:

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

On Sun, 20 Sep 2015 20:41:26 -0300 Antonio Terceiro 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

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

Am 21.09.2015 um 01:59 schrieb Antonio Terceiro: > On Sun, 20 Sep 2015 20:41:26 -0300 Antonio Terceiro > 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

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

On Thu, Aug 06, 2015 at 06:17:08PM +1000, Brian May 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[571]:

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

Am 21.09.2015 um 02:43 schrieb Michael Biebl: > 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 ... as enabled

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

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

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

On Thu, 6 Aug 2015 at 19:56 Brian May b...@debian.org wrote: Then again, maybe I was premature; I think I should do a reboot and redo the following: Really good theory, however after a reboot everything is fine: [brian:~] % for i in /sys/class/drm/*/*/status ; do echo $i ; done

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

On Thu, 6 Aug 2015 at 21:29 Michael Biebl bi...@debian.org wrote: Is another process blocking suspend? What's the output of systemd-inhibit? prune# systemd-inhibit Who: NetworkManager (UID 0/root, PID 535/NetworkManager) What: sleep Why: NetworkManager needs to turn off

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

Am 06.08.2015 um 12:07 schrieb Brian May: On Thu, 6 Aug 2015 at 19:56 Brian May b...@debian.org wrote: Then again, maybe I was premature; I think I should do a reboot and redo the following: Really good theory, however after a reboot everything is fine: [brian:~] % for i in

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

On Thu, 6 Aug 2015 at 18:31 Michael Biebl bi...@debian.org wrote: Do you use an external monitor? If logind detects an external monitor, it suppresses any suspend requests. Yes, I saw that code. There should be no reason for it to detect in external monitor, however that doesn't mean it isn't