Linux

63639 readers

391 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 6 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

My KDE Neon won't suspend automatically...what's blocking power management? (lemmy.world)

submitted 2 months ago* (last edited 2 months ago) by iturnedintoanewt@lemmy.world to c/linux@lemmy.ml

8 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] iturnedintoanewt@lemmy.world 2 points 2 months ago* (last edited 2 months ago) (1 children)

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 2 months ago (1 children)

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

[–] iturnedintoanewt@lemmy.world 1 points 2 months ago (1 children)

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 months ago* (last edited 2 months ago)

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

To clarify, systemctl stop libvirtd should do it.