I think this is a regression but I don't when it happened exactly. I have my laptop set to be at 100% screen brightness when plugged in (along with Performance mode), and at 40% screen brightness (+Balanced mode) when running on battery. And yet when I unplug it, the power profile changes as expected, but the screen brightness stays at 100%. My laptop is powered by an Anker USB-C dongle which also includes an HDMI port I use to extend my screen on an external monitor. Both the internal and external display are on while in use. System settings says 6.2.1 but it's just 'cause I'm in the middle of a snapshot update, this is for 6.2.0 (haven't restarted yet to check if it's been fixed on 6.2.1) Thanks Operating System: openSUSE Tumbleweed 20241016 KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.7.3 Kernel Version: 6.11.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M
Created attachment 175105 [details] Journal log
``` Operating System: CachyOS Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.4-5-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: G3 3500 ``` I'm facing the same issue on my system.
And also my other system: Operating System: CachyOS Linux KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.4-3-cachyos-deckify (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen Z1 Extreme Memory: 15.3 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Ally X RC72LA_RC72LA System Version: 1.0
I noticed that sometimes the brightness change works, there is no pattern however.
*** Bug 495126 has been marked as a duplicate of this bug. ***
Same problem with 6.2.2 on my dell xps
I've been experiencing this *intermittently* on git master as well. Most of the time it doesn't work, but some of the time it does. I have not been successful in figuring out the pattern yet.
*** Bug 495458 has been marked as a duplicate of this bug. ***
This is still happening for me. System details: Operating System: openSUSE Tumbleweed 20241127 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.8-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520
Thanks for the reports, everyone. I think the underlying cause of Bug 497362 might be somehow related to this one here as well (in a nutshell: PowerDevil's list of brightness devices isn't quite up to date at the time that the profile changes). Not entirely sure. Linking the other bug, in the hope that a fix for that one fixes or improves this one as well.
*** Bug 498277 has been marked as a duplicate of this bug. ***
Hi folks, I just pushed a fix for Bug 497362. Given the nature of that fix, which only concerns initial startup, I don't think that it fixes the problem described here. I'm still curious about test reports though, the fix for that bug will be in Plasma starting with 6.3 Beta 2. I also have a second patch set in the works that should generally increase robustness of profile-based brightness settings, and would always limit them to internal displays (no special cases for "sometimes external monitors will be adjusted"). I'll CC this bug once that merge request gets uploaded, but again, hard to say if it will improve this particular case.
(In reply to Jakob Petsovits from comment #12) > Hi folks, I just pushed a fix for Bug 497362. Given the nature of that fix, > which only concerns initial startup, (...) Well... I should say "mainly concerns initial startup". It would also make a difference if the internal display is briefly disconnected for whatever reason. I'm not quite sure how KWin's list of displays responds to all kinds of events, and if it briefly marks the internal display as removed while the display configuration change is happening, the merged fix *could* conceivably fix this as well. Hence the request for more testing after Plasma 6.3 Beta 2 (or on the master branch, if you have a development build).
Git commit 5460428e2dd1d7bac01ccbad23f501161635bd35 by Jakob Petsovits. Committed on 20/02/2025 at 01:57. Pushed by jpetso into branch 'master'. actions/screenbrightnesscontrol: More robust against display changes To avoid weird racy behavior in the case where an external monitor may have been added prior to the internal display, we now always limit the set of displays affected by profile state configuration to internal displays. This will make the "Change screen brightness" option disappear from the Power Management KCM for systems without internal display. No big loss for users of desktop PCs with only external monitors and no batteries, their KCM is now tidier and Wayland users still have brightness sliders available in the Display Configuration KCM in addition to the Brightness and Color applet. Also simplify conditions: the check for higher-than-min isn't needed, so we don't have to duplicate it in the `displayAdded` handler. `ScreenBrightnessController::setBrightness()` will already clamp brightness to a value between min and max brightness. Lastly, profile brightness is now also applied on `displayAdded`. This will avoid future bugs in case we ever have more than one internal display, one that might turn off and back on. (The case of the first internal display appearing and disappearing is already handled by `PowerDevil::Core` deleting the action if unsupported.) Related: bug 498771 M +28 -27 daemon/actions/bundled/screenbrightnesscontrol.cpp M +6 -3 daemon/actions/bundled/screenbrightnesscontrol.h M +12 -0 daemon/controllers/screenbrightnesscontroller.cpp M +7 -0 daemon/controllers/screenbrightnesscontroller.h https://invent.kde.org/plasma/powerdevil/-/commit/5460428e2dd1d7bac01ccbad23f501161635bd35
Git commit 6c875c360caadcc828c56e7a8831727d77ce75b0 by Jakob Petsovits. Committed on 20/02/2025 at 01:57. Pushed by jpetso into branch 'master'. actions/screenbrightnesscontrol: Only enable for systems with battery Users with only the AC Power profile aren't getting anything useful from this setting in the Power Management KCM, it's rather more confusing than it helps. This change complements the previous commit that limited profile-based screen brightness changes to internal displays only. Recommended alternatives for setting screen brightness are the Brightness and Color applet and the Display Configuration KCM, both of which allow setting brightness separately for each display. Related: bug 498771 M +12 -1 daemon/actions/bundled/screenbrightnesscontrol.cpp M +1 -0 daemon/actions/bundled/screenbrightnesscontrol.h https://invent.kde.org/plasma/powerdevil/-/commit/6c875c360caadcc828c56e7a8831727d77ce75b0
Git commit 06260f7785738fe45fdcd60e1c2bbd6bd3ee2bde by Jakob Petsovits. Committed on 21/02/2025 at 07:06. Pushed by jpetso into branch 'Plasma/6.3'. actions/screenbrightnesscontrol: More robust against display changes To avoid weird racy behavior in the case where an external monitor may have been added prior to the internal display, we now always limit the set of displays affected by profile state configuration to internal displays. This will make the "Change screen brightness" option disappear from the Power Management KCM for systems without internal display. No big loss for users of desktop PCs with only external monitors and no batteries, their KCM is now tidier and Wayland users still have brightness sliders available in the Display Configuration KCM in addition to the Brightness and Color applet. Also simplify conditions: the check for higher-than-min isn't needed, so we don't have to duplicate it in the `displayAdded` handler. `ScreenBrightnessController::setBrightness()` will already clamp brightness to a value between min and max brightness. Lastly, profile brightness is now also applied on `displayAdded`. This will avoid future bugs in case we ever have more than one internal display, one that might turn off and back on. (The case of the first internal display appearing and disappearing is already handled by `PowerDevil::Core` deleting the action if unsupported.) Related: bug 498771 (cherry picked from commit 5460428e2dd1d7bac01ccbad23f501161635bd35) M +28 -27 daemon/actions/bundled/screenbrightnesscontrol.cpp M +7 -3 daemon/actions/bundled/screenbrightnesscontrol.h M +12 -0 daemon/controllers/screenbrightnesscontroller.cpp M +7 -0 daemon/controllers/screenbrightnesscontroller.h https://invent.kde.org/plasma/powerdevil/-/commit/06260f7785738fe45fdcd60e1c2bbd6bd3ee2bde
Git commit 984548ffb494d353365c024d843126872b323dba by Jakob Petsovits. Committed on 21/02/2025 at 07:06. Pushed by jpetso into branch 'Plasma/6.3'. actions/screenbrightnesscontrol: Only enable for systems with battery Users with only the AC Power profile aren't getting anything useful from this setting in the Power Management KCM, it's rather more confusing than it helps. This change complements the previous commit that limited profile-based screen brightness changes to internal displays only. Recommended alternatives for setting screen brightness are the Brightness and Color applet and the Display Configuration KCM, both of which allow setting brightness separately for each display. Related: bug 498771 (cherry picked from commit 6c875c360caadcc828c56e7a8831727d77ce75b0) M +12 -1 daemon/actions/bundled/screenbrightnesscontrol.cpp M +1 -0 daemon/actions/bundled/screenbrightnesscontrol.h https://invent.kde.org/plasma/powerdevil/-/commit/984548ffb494d353365c024d843126872b323dba
It is working on 6.3.2.
I noticed that by default the brighness is not going to 100% again after the cable is reconnected. I haven't had the time to manually set everything in the system settings again. So I'm saying that just the default as not as good as it could've been.