Bug 443213

Summary: Allow configuring the brightness adjustment increment, as with the volume adjustment increment
Product: [Applications] systemsettings Reporter: C0D3 M4513R <while.stuck+kde>
Component: kcm_powerdevilAssignee: Plasma Bugs List <plasma-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: kde, kde, natalie_clarius, nate, random1123581321, raphael.kde, typingcat, while.stuck+kde
Priority: NOR    
Version First Reported In: 5.22.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description C0D3 M4513R 2021-10-02 00:50:49 UTC 
SUMMARY

The Change of Brightness per Key-press is hard-coded in this program.
My proposal is to add a way to manually change this, via a dbus-interface or a config-file or System Settings

STEPS TO REPRODUCE
1. Press Screen Brightness Down
2. Observe -5% change.
3. Run `qdbus local.org_kde_powerdevil /org/kde/Solid/PowerManagement/Actions/BrightnessControl org.kde.Solid.PowerManagement.Actions.BrightnessControl.brightnessSteps` and verify it outputs 20


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.8-arch1-1
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Comment 1 Raphaël Jakse 2021-10-16 23:14:42 UTC 
Additionally, it would be nice if the lowest 5% were done by increments/decrements of 1%. In a dark screen, 5% is too high and 0% is turned off (actually, 1% is still a bit too high on this screen for my eyes, being able to set 0.5% would be perfect).

My current workaround it to use the wheel on the battery icon (which does increments of 1%), or setting the /sys/class/backlight/*/brightness file.
Comment 2 Raphaël Jakse 2021-10-16 23:15:54 UTC 
I meant in a dark room, not screen, sorry.
Comment 3 Nate Graham 2021-11-23 17:34:37 UTC 
*** Bug 445906 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2025-06-17 19:16:50 UTC 
*** Bug 430051 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2025-06-17 19:17:19 UTC 
*** Bug 485753 has been marked as a duplicate of this bug. ***