SUMMARY Power management does not work in neon unstable regardless my laptop is connected or not. STEPS TO REPRODUCE 1. open 'Energy Saving' KCM 2. set the timeout of 'Dim screen', 'Screen Energy Saving' and 'Suspend session' (and select 'Sleep') to 1 minute 3. do not use your machine for 1 minute OBSERVED RESULT nothing happens EXPECTED RESULT the power management works SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.26.80 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Graphics Platform: Wayland
And powerdevil is running?
A process called org_kde_powerdevil is running.
I have also noticed this on Unstable. Setting status to Confirmed. paul@neon-dev [10:24:38]:~$ ps aux|grep power root 1099 0.0 0.1 239860 8976 ? Ssl 08:59 0:00 /usr/libexec/upowerd paul 1332 0.0 0.5 561128 43444 ? Ssl 08:59 0:00 /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil paul 29765 0.0 0.0 6612 2332 pts/1 S+ 10:24 0:00 grep --color=auto power
The same machine, dual booted into Neon User, works OK. Adding "regression" keyword.
*** Bug 465017 has been marked as a duplicate of this bug. ***
Is this daemon unmaintained?
No
*** Bug 465778 has been marked as a duplicate of this bug. ***
Now reproducible on Neon User 5.27 (Summary and version updated) Only happens in Wayland (keyword added)
*** Bug 465806 has been marked as a duplicate of this bug. ***
No longer reproducible on neon unstable after installing updates 2 hours ago. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: Wayland
I can confirm, it is working again!
Still not working for me with all latest updates. I also disabled bluetooth and closed out of any background programs I use (MEGASync, Nicotine+) and confirmed from Status and Notifications applet that no application is inhibiting sleep. Image1: https://i.imgur.com/VcWMxZS.png Image 2: https://i.imgur.com/Z4SIdyd.png
Accidentally reopened, I will wait for plasma version 5.27.80 to make it into KDE Neon user edition and see if that fixes it.
Mine kind of still work on 5.27 with my laptop. It now goes into deep sleep or somethin because i cannot wake it up unless i press a button on the built in keyboard. i used to wake up my laptop by pressing on my external keyboard or moving mouse. i have hibernate and swap disabled so i do not know
We're getting more reports of this, so I'm re-opening it. Seems flaky rather than 100% broken for everyone, which is the worst kind of bug. FWIW I cannot reproduce this issue by setting the Tim Screen, Screen Energy Saving, and Suspend Session options to trigger after 1 minute, as in the original report.
Are y'all sure that nothing was blocking sleep at the time? The battery & Brightness widget will tell you.
> Are y'all sure that nothing was blocking sleep at the time? The battery & Brightness widget will tell you. No it was not. The screen turned into the lockscreen and eventually locked at some time, but it was not turning off. I think 5.27.0 has no fix included, it is fixed on unstable only. Probably in 5.27.1
same here, wayland with plasma 5.27.0 on fedora 37 Setting screen-dim to 1 minute, sreen energy saving to 2 min and waiting: - after 1 min, neither laptop screen nor the display-port attached 2nd 4k monitor are getting dim (in x11, only the laptop was dimmed, not the dp-attached monitor) - after 2 min, no poweroff of laptop nor dp-attached screen. - sometime later, the screen-lock comes active. I found no combination of settings that really turn off both displays as they did in 5.26.x Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31,1 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: LENOVO
(In reply to Nate Graham from comment #17) > Are y'all sure that nothing was blocking sleep at the time? The battery & > Brightness widget will tell you. yes 100 percent. The screen blocking was unchecked. I can only wake up my computer now by pressing something on my latop built in keyboard. Mouse click or external keyboard no longer wakes it
*** Bug 466147 has been marked as a duplicate of this bug. ***
Same here with Fedora 37, 5.27.0, 5.103.0, Wayland. Desktop with Radeon RX 6700 XT graphics, None of my three displays will turn off.
interestingly, the functionality of powerdevil seems to work as expected: 1) screen lock enter screen-lock manually (meta-L) and press ESC. Laptop screen and DP-monitor get powered off 2) use krunner and give the command 'dim half' ok, this affects only the laptop screen, but it works (never seen this on my external monitor to work, so my expectations are low :-) ) It seems to have troubles only if the 'screen locking' kicks in after the timeout or if powerdevil needs to apply the settings of 'systemsettings5 > energy saving'
Is everyone here using multiple screens? And is at least one of them a DisplayPort screen?
In my case, yes. All three are DisplayPort.
(In reply to Nate Graham from comment #24) > Is everyone here using multiple screens? > > And is at least one of them a DisplayPort screen? I’m experiencing this bug with a single DisplayPort screen. Using the non-free Nvidia driver.
My report 466147 was marked as a duplicate. I my case there is no display port or multi monitor involved.
I have the same problem, Single monitor, hdmi port. All was working on plasma 5.26.5 on same hardware. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland From the journal, when I tried to change the settings I got :- org_kde_powerdevil[1766]: org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported followed by :- org_kde_powerdevil[1766]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" hope this helps,
*** Bug 466215 has been marked as a duplicate of this bug. ***
We're getting a lot of reports of power management not working properly in Plasma 5.27, but there appear to be a few root causes. I'll untangle this and find the distinct issues, then make them parent bugs for duplicates. In the meantime, it would be appreciated if people could avoid posting, "me too!" comments. Instead, filing a new bug report for your specific issue would be more helpful, and I'll mark it as a duplicate of the correct one.
Graeme, your issue seems slightly different if no DisplayPort screens are involved. Can you submit a new bug report for it? Thanks!
I've been trying to reproduce this issue and I have not been able to. I'm using wayland and display ports, using the ddc backend. I think it would be useful to try to tell the different variables apart before we can put together a fix. Would somebody please be able to test the following for me? - set the time to Dim screen or "screen energy saving" to 1 minute (so that you can wait without getting too bored). - Run "/usr/lib/org_kde_powerdevil --replace" on a terminal - Share here the output you get Maybe that way we can find something complaining that it doesn't work.
$ /usr/libexec/org_kde_powerdevil --replace org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed kf.idletime: Could not find any system poller plugin QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter org.kde.powerdevil: Handle button events action could not check for screen configuration org.kde.powerdevil: The profile "AC" tried to activate "DimDisplay" a non-existent action. This is usually due to an installation problem, a configuration problem, or because the action is not supported org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Okay, then it seems like a packaging problem in neon, it's fixed in unstable but not stable: https://invent.kde.org/neon/kde/kidletime/-/commit/716c5b3f7b74aaa69d3f6bf7827b7f03c95e769c You can double-check by seeing whether the following file is available: /usr/lib/*/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeWaylandPlugin.so Moving to neon, if somebody can reproduce this problem outside of KDE Neon, please say so and we'll check if either your distro has the same problem or there's a different problem on top.
Seems to be missing on Fedora ``` [root@blacky org.kde.kidletime.platforms]# ls KF5IdleTimeXcbPlugin0.so KF5IdleTimeXcbPlugin1.so ```
I ran it on Fedora 37 but the plugin doesn't appear to be there either. No package appears to provide it either.
I don't know if this is related but on both my machines logout clears the screen then hangs forever. Touching the power button shuts down the machine.
I've added this now to KDE neon, please upgrade
I've confirmed with the Fedora team that they also had this problem and they're looking into addressing it.
(In reply to Aleix Pol from comment #39) > I've confirmed with the Fedora team that they also had this problem and > they're looking into addressing it. This has been fixed on Fedora here: https://src.fedoraproject.org/rpms/kf5-kidletime/c/2a096ad8d7e9ab9a838156021991d86e76971117?branch=rawhide It will take a few minutes/hours to reach the stable servers. For those who want it **now**, you can use our COPR: https://copr.fedorainfracloud.org/coprs/g/kdesig/kde/
Closing as a downstream issue.
*** Bug 466267 has been marked as a duplicate of this bug. ***
I don't understand why this is marked as closed when the problem has not been fixed. Running openSUSE Tumbleweed/KDE 5.27.1 and the problem still exists. I can switch to X11 and it works just fine. It only fails to work in Wayland. This is on a laptop with no external screen attached.
(In reply to Wilson Phillips from comment #43) > I don't understand why this is marked as closed when the problem has not > been fixed. > It's been fixed on KDE side. Nothing they can do about it. > Running openSUSE Tumbleweed/KDE 5.27.1 and the problem still exists. I can > switch to X11 and it works just fine. It only fails to work in Wayland. This > is on a laptop with no external screen attached. This is something openSUSE needs to fix the same way Neon or we (Fedora) did. Again, everything is fine on the KDE side of things.
I have the same issue with Nobara (Fedora based). I reported it [here](https://gitlab.com/GloriousEggroll/nobara-images/-/issues/96) TLDR; ```sh kf.idletime: Could not find any system poller plugin QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter org.kde.powerdevil: Handle button events action could not check for screen configuration ``` Appears not to be a bug from KDE itself.
*** Bug 466428 has been marked as a duplicate of this bug. ***