17
submitted 3 days ago* (last edited 3 days ago) by iturnedintoanewt@lemmy.world to c/linux@lemmy.ml

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!

top 8 comments
sorted by: hot top controversial new old
[-] nathan@piefed.alphapuggle.dev 7 points 3 days ago

Try sudo systemd-inhibit --list

[-] iturnedintoanewt@lemmy.world 2 points 3 days ago* (last edited 3 days ago)

Thanks! 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.

[-] jaxxed@lemmy.world 2 points 3 days ago

Is there no reason to suspect your vm states are the cause?

[-] iturnedintoanewt@lemmy.world 1 points 3 days ago

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?

[-] jaxxed@lemmy.world 2 points 2 days ago* (last edited 2 days ago)

You could shut down your vm service temporarily and see if it works.

To clarify, systemctl stop libvirtd should do it.

[-] ada@piefed.blahaj.zone 4 points 3 days ago

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)

[-] PanaX@lemmy.world 3 points 3 days ago

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.

[-] mybuttnolie@sopuli.xyz 2 points 3 days ago

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...

this post was submitted on 13 Dec 2025
17 points (100.0% liked)

Linux

57274 readers
957 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS