https://bugs.kde.org/show_bug.cgi?id=523988
Jakob Petsovits <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/powerdevil/-/commit/78a9 |ma/powerdevil/-/commit/e49c |6e9ddb3a4cf2eb064c2b032864d |98f353145f30facb58a2c90adc6 |b7c9963a7 |ab124270f --- Comment #15 from Jakob Petsovits <[email protected]> --- Git commit e49c98f353145f30facb58a2c90adc6ab124270f by Jakob Petsovits. Committed on 27/10/2026 at 21:32. Pushed by jpetso into branch 'Plasma/6.8'. 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. (cherry picked from commit 0ca9bdb82c927518ca60eef589bd89ec6192ef6d) Co-authored-by: Petru Mare <[email protected]> M +14 -3 daemon/controllers/kwinbrightness.cpp M +2 -0 daemon/controllers/screenbrightnesscontroller.cpp https://invent.kde.org/plasma/powerdevil/-/commit/e49c98f353145f30facb58a2c90adc6ab124270f -- You are receiving this mail because: You are watching all bug changes.
