On Sat, Mar 28, 2020 at 2:36 PM Samuel Sieb <samuel@xxxxxxxx> wrote: > From the working suspend, can you look at the logs and see if there are > any messages indicating the process? If there are, you could compare > them against the one that didn't work. There are no gnome or systemd related messages as to why target sleep was reached. If I push the power button, I get an explicit message from systemd-logind that it was pushed - same for the lid. But nothing for a GNOME Shell automatic suspend timeout. Mar 29 14:58:36 flap.local kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 29 14:58:36 flap.local kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 29 14:58:36 flap.local NetworkManager[638]: <info> [1585515516.3083] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 29 14:58:36 flap.local NetworkManager[638]: <info> [1585515516.3088] device (p2p-dev-wlp108s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 29 14:58:36 flap.local NetworkManager[638]: <info> [1585515516.3105] manager: NetworkManager state is now ASLEEP Mar 29 14:58:36 flap.local systemd[1]: Reached target Sleep. Mar 29 14:58:36 flap.local systemd[1]: Starting Suspend... Mar 29 14:58:36 flap.local systemd-sleep[8706]: Suspending system... Mar 29 14:58:36 flap.local kernel: PM: suspend entry (deep) Mar 29 14:58:36 flap.local kernel: Filesystems sync: 0.015 seconds -- Chris Murphy _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
