https://bugs.kde.org/show_bug.cgi?id=523988
Jakob Petsovits <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Latest Commit| |https://invent.kde.org/plas | |ma/powerdevil/-/commit/78a9 | |6e9ddb3a4cf2eb064c2b032864d | |b7c9963a7 Resolution|--- |FIXED --- Comment #14 from Jakob Petsovits <[email protected]> --- Git commit 78a96e9ddb3a4cf2eb064c2b032864db7c9963a7 by Jakob Petsovits, on behalf of Petru Mare. Committed on 27/10/2026 at 19:10. Pushed by jpetso into branch 'master'. Fix screens staying dimmed after losing brightness control When a DDC/CI write fails (for example after the monitor powered down and libddcutil invalidated its handle), DDCutilDisplay gives up on the display and KWin unsets its brightness device. KWinDisplayDetector then drops the output, but KWin keeps applying the last dimming factor in software, so a screen that was idle-dimmed to 30% stays at 30% until KWin restarts. Re-detecting the output didn't help either: the new KWinDisplayBrightness assumed a dimming of 1.0, so setting 1.0 was a no-op. Reset the dimming of outputs we stop managing, start from the dimming KWin reports, and apply the current dimming ratio to newly detected displays. M +14 -3 daemon/controllers/kwinbrightness.cpp M +2 -0 daemon/controllers/screenbrightnesscontroller.cpp https://invent.kde.org/plasma/powerdevil/-/commit/78a96e9ddb3a4cf2eb064c2b032864db7c9963a7 -- You are receiving this mail because: You are watching all bug changes.
