I tried to set the display to dim in 3 and 2 minutes. In both cases the display actualy dimmed in 1:30 and 1 minute respectively. I tested on battery and on ac power with same results. Reproducible: Always Steps to Reproduce: 1. Open Enrgy Saving 2. Set dim display after 2 minutes Actual Results: Display is dimmed in 1 minute Expected Results: Display dimmed in 2 minutes I think this is not specific to 4.9, I have noticed this bug from previous versions.
Not sure if bug or a feature. My display dims 2 times: once in a half of dim timer, for about 50% of current brightness and on a dim timer, to 10%.
The bug is still present in 4.9.4. Anyone can confirm?
(In reply to comment #1) > Not sure if bug or a feature. My display dims 2 times: once in a half of dim > timer, for about 50% of current brightness and on a dim timer, to 10%. Maybe you are right. It could be a feature, however for me it has more sense that the time you provide should be used to start dimming and not to complete dimming with intermediate steps.
Looks like powerdevil has always behaved like this. It seems to have inherited this behaviour from KDE4PowerSave, its predecessor(?). I'm not sure how much sense this makes, however. Dario?
*** Bug 299980 has been marked as a duplicate of this bug. ***
*** Bug 299979 has been marked as a duplicate of this bug. ***
Are we still dimming using this strategy? We talked about this at the sprint, what was the decision if any?
Closing the bug for inactivity. Will try to improve in 2.0 anyway.
*** Bug 326526 has been marked as a duplicate of this bug. ***
*** Bug 323041 has been marked as a duplicate of this bug. ***
Created attachment 108874 [details] Screenshot of dim screen setting
This is still open. Setting "Dim screen" to "3 min" makes the display dim after 90s (instead of 180s). Unchecking "Dim screen" disables dimming, so it is likely due to this setting. System settings 5.11.3 on KDE neon. Can't believe this has been open for 5+ years.
Created attachment 115877 [details] Power settings not obeyed Hi, this bug still exists in Plasma 5.14.1 (on openSUSE Tumbleweed). With the settings in this screenshot, it appears to dim to about 50% brightness after 2.5 minutes (half of my configured 5 minutes). But what is more strange is that it goes into yet another dimmed state of about 10% brightness at the 5 minute mark, and finally powers off the screen entirely at 6 minutes.
As Oliver said in 2013, it looks like this is the intended behaviour since it was first written (8 years ago?). https://github.com/KDE/powerdevil/blame/master/daemon/actions/bundled/dimdisplay.cpp#L64 At 50% the set idle duration, it dims to 50% brightness. At 75% the set idle duration, it dims to 12.5% brightness. At 100% the set idle duration, it dims to 0% brightness. We could maybe use different values, say 90% brightness, then 70% brightness, before dropping to 0% at the specified time. I wonder if there'd be issues with changing it to 5/4 (125% idle duration) and 3/2 (150% idle duration) so that it doesn't start dimming before the user's explicitly defined value.
*** Bug 407681 has been marked as a duplicate of this bug. ***
*** Bug 411497 has been marked as a duplicate of this bug. ***
If the behaviour is not changed, it would be nice to have the actual behaviour explained in the config panel. The current experience certainly isn't as intuitive as it could be.
This bug is still present, KDE 5.24.4. There are 5 proposed solutions, ranked from worst to best. 1. Do nothing, it works as intended. 2. Keep the same behavior, except dim less (90%, 75%). This will cause just as much end-user confusion, while also upsetting people who are used to the current behavior. 3. Keep the same behavior, but document it in the settings interface. This is the least we could do, should ruffle no feathers, and won't even unbalance the UI since that page already contains several long textual explanations. 4. Keep the behavior as is, except change the dimming times to be 1, ⁵⁄₄, ³⁄₂ (instead of ½, ¾, 1), so the screen stays full brightness until the requested dimming time. 5. Remove this unnecessary feature. Dim 50% at the requested time, and let "Screen Energy Saving: Switch off" do the rest. "Do nothing" has been the KDE response for a decade at this point, and yet it is clearly the wrong answer. There is no way to read "Dim screen: After 3 minutes" to mean "50% at 1:30".
I sent an MR to fix this https://invent.kde.org/plasma/powerdevil/-/merge_requests/213
*** Bug 473562 has been marked as a duplicate of this bug. ***
Git commit 14647dc6ffd1104c1c0ab393518de8a65cb39d70 by Nate Graham, on behalf of Konstantin Kharlamov. Committed on 25/08/2023 at 16:46. Pushed by ngraham into branch 'master'. dimdisplay: only dim the screen at configured dim time The current logic is completely broken: 1. It disables the screen at `m_dimOnIdleTime` even though disabling the screen is handled elsewhere with a separate timeout, and the logic here has prefix "Dim*" so has nothing to do with disabling it. 2. It does not follow the timeout configured by a user (that is the `m_dimOnIdleTime`) and instead dims the screen at completely arbitrary 50% and 75% periods of the configured time. Let's get rid of all that and only do exactly what the user asked: dim the screen at `m_dimOnIdleTime`. FIXED-IN: 5.27.8 M +10 -14 daemon/actions/bundled/dimdisplay.cpp https://invent.kde.org/plasma/powerdevil/-/commit/14647dc6ffd1104c1c0ab393518de8a65cb39d70
Git commit dc4a286037a802f3c18512e761b89082740aa1e9 by Konstantin Kharlamov. Committed on 29/08/2023 at 01:42. Pushed by ngraham into branch 'Plasma/5.27'. dimdisplay: only dim the screen at configured dim time The current logic is completely broken: 1. It disables the screen at `m_dimOnIdleTime` even though disabling the screen is handled elsewhere with a separate timeout, and the logic here has prefix "Dim*" so has nothing to do with disabling it. 2. It does not follow the timeout configured by a user (that is the `m_dimOnIdleTime`) and instead dims the screen at completely arbitrary 50% and 75% periods of the configured time. Let's get rid of all that and only do exactly what the user asked: dim the screen at `m_dimOnIdleTime`. FIXED-IN: 5.27.8 M +10 -14 daemon/actions/bundled/dimdisplay.cpp https://invent.kde.org/plasma/powerdevil/-/commit/dc4a286037a802f3c18512e761b89082740aa1e9
Is there some migration so that the currently-configured timeout doesn't suddenly double at the next upgrade? Some of us have since configured our systems to compensate for the 50% time behaviour.
(In reply to Paul Gideon Dann from comment #23) > Is there some migration so that the currently-configured timeout doesn't > suddenly double at the next upgrade? Some of us have since configured our > systems to compensate for the 50% time behaviour. There isn't, but if you think it is a real problem I think it might be possible to revert the change from stable and just leave it be a breaking change for the next big 6.0 release…
Nah; this isn't enough of a problem for me for it to be worth delaying the fix. But thanks for confirming that there's no config migration. I'll just keep an eye on the behaviour when upgrading.
There's no real way for us to know whether a person set the time they did because that's the way they wanted it and they never noticed the bug, or because they did notice the bug and were manually working around it. For that reason, any such migration code would probably cause as many problems as it would potentially solve. As a general matter, people who find workarounds for issues are generally expected to undo their workarounds once the issues are fixed.