https://bugs.kde.org/show_bug.cgi?id=494815
Jakob Petsovits <jpe...@petsovits.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Version|6.2.4 |6.2.0 Version Fixed In| |6.2.3 Latest Commit| |https://invent.kde.org/plas | |ma/kwin/-/commit/4f18aae673 | |209473fe3c85ae7b52bd9f85961 | |a14 Status|REPORTED |RESOLVED --- Comment #11 from Jakob Petsovits <jpe...@petsovits.com> --- Re. original issue (Comment #0) filed by Arnab Bose: I believe this was a symptom of KWin/Wayland using either hardware brightness or software brightness adjustments, depending on what's available. It would work like this: 1. Hardware brightness controls are available for your screen, you set it to e.g. 50%, then restart your session. 2. Hardware brightness controls somehow aren't getting initialized correctly, but the screen is still at 50% hardware brightness. However, KWin doesn't know about hardware brightness now, so it uses software dimming to reduce brightness to 50%. Combined with the existing hardware brightness, this makes for only 25% and explains why e.g. ddcutil won't restore brightness back to to 100% in that session. This was fixed in KWin by https://invent.kde.org/plasma/kwin/-/merge_requests/6670 which was first released with Plasma 6.2.3. Not sure if we had a bug report or which one it was, I'll just close this as fixed. If the original reporter (Arnab) still experiences this issue, please reopen this bug with a status update of how your system is behaving now. --- Oliver's dimming issue from Comment #10 is likely a different bug, which would be fixed by https://invent.kde.org/plasma/powerdevil/-/merge_requests/466 (and related MRs), shipping to users from Plasma 6.3 Beta 1 onwards. I'll regard this as unrelated to the original report. Please open a separate bug if you still find issues with this in Plasma 6.3. Thanks! -- You are receiving this mail because: You are watching all bug changes.