Running GNOME on a desktop PC, suspend has been working reliably and was configured to be triggered by the power button out fo the box.
I don't know what I've changed or if it was some package upgrade, but more often than not suspend is broken. When I press the power button now, I'm prompted for a shutdown. When I select "Suspend" from the system menu, nothing happens.
`systemd-inhibit` outputs:After a restart suspend works from system menu as well as power button, but after using applications for a while, It stops working. I need to log out and then can suspend.
How can I diagnose what the issue is?
I don't know what I've changed or if it was some package upgrade, but more often than not suspend is broken. When I press the power button now, I'm prompted for a shutdown. When I select "Suspend" from the system menu, nothing happens.
`systemd-inhibit` outputs:
Code:
$ systemd-inhibit WHO UID USER PID COMM WHAT WHY MODE ModemManager 0 root 987 ModemManager sleep ModemManager needs to reset devices delayNetworkManager 0 root 960 NetworkManager sleep NetworkManager needs to turn off networks delayUPower 0 root 1291 upowerd sleep Pause device polling delayGNOME Shell 1000 jost 1947 gnome-shell sleep GNOME needs to lock the screen delayjost 1000 jost 2115 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses blockjost 1000 jost 2115 gsd-media-keys sleep GNOME handling keypresses delayjost 1000 jost 2117 gsd-power sleep GNOME needs to lock the screen delayjost 1000 jost 1916 gnome-session-b sleep user session inhibited block8 inhibitors listed.How can I diagnose what the issue is?
Statistics: Posted by jost-s — 2024-12-15 23:47 — Replies 2 — Views 93