So…As I installed KDE Neon recently, it worked and autosuspended perfectly after 15min, which is what’s set on Power Management settings. However, I’ve noticed after installing and configuring all the rest of the apps, it’s no longer the case. I mean, it DOES suspend if I manually click the Suspend in the start menu, or if I hit the suspend key from my keyboard. But it won’t do it on its own.
I initially suspected SMPlayer, which in the Ubuntu 24.04 repos has a long standing issue about this (will suspend when playback stopped, but not when paused). But after installing the newest flatpak…and even with SMPlayer closed, it’s still not suspending. What else could be blocking Power Management from suspending my PC? How can I troubleshoot this?
Thanks!
Try
sudo systemd-inhibit --listThanks! This is what I’m getting here. If I understand this correctly, this is a list of POSSIBLE inhibitors…not which one was triggered last time blocking the actual suspension right?
WHO UID USER PID COMM WHAT WHY > Libvirt 0 root 77709 libvirtd shutdown Virtual machines need to be saved > ModemManager 0 root 1183 ModemManager sleep ModemManager needs to reset devices > NetworkManager 0 root 1087 NetworkManager sleep NetworkManager needs to turn off networks > UPower 0 root 1896 upowerd sleep Pause device polling > PowerDevil 1000 timonoj 2165 org_kde_powerde handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch KDE handles power events > Screen Locker 1000 timonoj 1878 kwin_wayland sleep Ensuring that the screen gets locked before going to sleep> 6 inhibitors listed. lines 1-9/9 (END)Having a second thought about this, it looks like Screen Locker might be the culprit. But I’m not completely sure. I really could see the desktop wasn’t even locked after a whole night. So maybe it failed to trigger? How can I look at…what’s inhibiting the screen from locking, now? Just like suspension, it works when manually triggered with Meta key + L.
Is there no reason to suspect your vm states are the cause?
Sure, I could suspect it…but how can I try to troubleshoot it? Is there a way to see what blocks the desktop from locking the screen?
I had a bug similar to this for years. I tried multiple distros, DEs, hdmi cables, display port cables, etc etc. I didn’t want suspend, but I really need screen blanking. I finally had a revelation deep in some forum somewhere that mentioned some feature on my monitor. I forget what it was exactly, but it was an ‘auto’ something that prevented the computer itself from doing anything.
Odd, but possible.
i had the autosuspend issue with mint. tried to troubleshoot it for two years. every now and then i thought i found the solution, but weeks or months later the issue reappeared, and i swear i started balding because of that shit! thought it might be because I’m using a tv as a monitor, but other distros didn’t have the same issue, they just had much worse issues. recently tossed my nvidia and got an amd gpu, switched to ultramarine kde. I’m living with a lot of minor bugs now, but it suspends! funny thing is that mint didn’t recognize the tv after waking from suspend after switching to amd…
Steam often does it for me. But it should tell you what’s doing it in the task tray icon bar somewhere (not near a computer at the moment, so I can’t be specific)
