Created attachment 115509 [details] systemd logs messages Since update to Linux kernel 4.1.0-rc1 my laptop stopped to suspend after Lid is closed properly. The first time after fresh reboot it does proper suspend, the rest suspend tries - doesn't work. Only manual systemctl suspend works. Here is the attached journalctl logs. As you can see, after reboot I got proper suspend: ======== May 02 12:57:25 x systemd-logind[1518]: Lid closed. May 02 12:57:25 x systemd-logind[1518]: Suspending... May 02 12:57:25 x systemd[1]: Starting i3lock... May 02 12:57:25 x systemd[1]: Started i3lock. May 02 12:57:25 x systemd[1]: Reached target Sleep. May 02 12:57:25 x systemd[1]: Starting Sleep. May 02 12:57:25 x systemd[1]: Starting Suspend... May 02 12:57:25 x systemd-sleep[2446]: Suspending system... ========= after that, I do Lid close once again: May 02 13:37:47 x systemd-logind[1518]: Lid closed. then I wait for 10 seconds while my system supposed to go sleep, but as nothing was happening I opened the Lid: May 02 13:37:56 x systemd-logind[1518]: Lid opened. decided to check maybe it needs some time to sleep or something like this: May 02 13:37:57 x systemd-logind[1518]: Lid closed. But almost 20 minutes of lid close did not work. May 02 13:53:34 x systemd-logind[1518]: Lid opened. Let me know if I can help you to debug the issue more, just let me know what to do.
Any update on this? Is there anything I can do to debug it deeper to provide you with more valuable information?
Created attachment 115654 [details] journalctl output with debug mode journalctl output after lid id closed: ======================================= May 08 17:17:27 x systemd-logind[1457]: Lid closed. May 08 17:17:27 x systemd[1]: Got notification message for unit systemd-logind.service May 08 17:17:27 x systemd[1]: systemd-logind.service: Got notification message from PID 145 7 (WATCHDOG=1) May 08 17:17:27 x systemd[1]: systemd-logind.service: got WATCHDOG=1 May 08 17:17:27 x systemd-logind[1457]: Multiple (5) displays connected. May 08 17:17:27 x systemd-logind[1457]: Refusing operation, as it is turned off. May 08 17:17:27 x systemd-logind[1457]: Multiple (5) displays connected. May 08 17:17:27 x systemd-logind[1457]: Refusing operation, as it is turned off. May 08 17:17:30 x wpa_supplicant[1549]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-58 noise=9999 txrate=270000 May 08 17:17:33 x dhclient[1983]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 May 08 17:17:41 x systemd[1]: Got notification message for unit systemd-journald.service May 08 17:17:41 x systemd[1]: systemd-journald.service: Got notification message from PID 1 024 (WATCHDOG=1) May 08 17:17:41 x systemd[1]: systemd-journald.service: got WATCHDOG=1 May 08 17:17:44 x dhclient[1983]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 May 08 17:17:49 x systemd-logind[1457]: Lid opened. xrandr output: ========================================== Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 32767 x 32767 eDP1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 310mm x 174mm 2560x1440 60.00*+ 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 1920x1200 59.95 1920x1080 59.93 1600x1200 60.00 1680x1050 59.95 59.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.80 59.96 1152x864 60.00 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis)
This really looks like a kernel issue (i.e. it reports displays plugged which aren't there anymore), and I am pretty sure has long been fixed. If not, please file a new bug against the kernel (unless there's strong indication there's really something bad in systemd, but I doubt it is, but in that case file a new bug on github systemd please)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.