*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When an application is requesting a sleep or screen wake lock, they're not being display in the "Display Configuration" or "Power Managment" Plasmoids. Applications tested Firefox - playing video or music Google Chrome - same as firefox Elisa - playing music I've also tested "systemd-inhibit --who="test sleep" --what="sleep" --why="testing sleep without screen lock" sleep infinity" but this does not show either. The actual functionality works i.e sleep/screen locks are inhibited but I don't normally shut down my PC I leave it to go to sleep, so before logging off I check to see if there are any wake locks that might prevent it but currently none of them are listed, which is made more annoying as Steam seems to want to permanently inhibit sleep. I have tested several differ distros and live USB's and they all seem to exhibit the same behaviour on my PC, the problem I have is that I have a laptop on the same distro and that works fine, hence I was hesitant to log a bug. STEPS TO REPRODUCE 1. Launch an application and perform activity that should generate a wake lock eg Play a YouTube video 2. Pin the Power Management or Display Configuration plasmoid 3. Note the lack of information about any wake locks OBSERVED RESULT No information about which application is displaying the wake locks EXPECTED RESULT Depending on the application, something like "Google Chrome is preventing sleep: Playing video" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 24 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Not sure if screenshots are allowed, but I can provide if needed
Found a work around to make the wake locks display, I just have no idea what it would work. Restarting through systemd does the trick: systemctl --user restart plasma-plasmashell.service
Does this mean that normally you restart plasma using `plasmashell --replace` or something? If so, don't do that. :) When using systemd integration, the expected way to restart Plasma is with `systemctl --user restart plasma-plasmashell.service`.
No no, I use the command above; systemctl --user restart plasma-plasmashell.service I just have no idea why this is even needed! :D
Is powerdevil running on the system? Does the issue reproduce in a new clean user account?
I can confirm that powerdevil is running and I experience the same problem with a second account. I have tried 3 or 4 different arch based OS's and they all exhibit the same behavior, even the live usb's.
Hu, how strange. FWIW I can't reproduce the issue myself in my built-from-source Plasma session on top of Fedora 40.
In my testing it only affects Arch based Distro's for me. If I try Neon for example, that works as expected.
Hmm, to me it sounds like there's an issue with the kernel version that Arch is shipping, or else all of these installs are missing a package that makes it work. Can you work with the Arch folks to determine what the problem is? If it turns out to be a Plasma issue, we can re-open this once we have a better idea of what it is.