All, I have twice noted a failure of my desktop to enter a Suspend state. I returned to my desk after a time to find no display on my monitors yet the power lamp solidly lit (it should have been flashing during Suspend). The machine was completely non-responsive to key presses or mouse movement and had to be restarted using the power button.
I am trying to troubleshoot this problem and have examined the journalctl log for the time that my machine should have suspended and find:
**systemd-logind[1552]:**The system will suspend now!
ModemManager[1632]: [sleep-monitor-systemd] system is about to suspend
NetworkManager[1652]: [1735872328.5671] manager: sleep: sleep requested (sleeping: no enabled: yes)
NetworkManager[1652]: [1735872328.5673] manager: NetworkManager state is now ASLEEP
systemd[1]: Reached target sleep.target - Sleep.
systemd[1]: Starting systemd-suspend.service - System Suspend…
systemd-sleep[12344]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
systemd-sleep[12344]: This is not recommended, and might result in unexpected behavior, particularly
systemd-sleep[12344]: in suspend-then-hibernate operations or setups with encrypted home directories.
systemd-sleep[12344]: Performing sleep operation ‘suspend’…
I know next to nothing about systemd. Can someone tell me if these log entries appear “normal?”
Can anyone suggest what my next steps should be?