You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a 10% on backlight seeing to prevent accidentally seeing it to
zero and losing visibility. Would be easy to make the lower limit
configurable.
Same problem here. After the look around, I noticed that math actual_brightness / max_brightness is not working for me. actual_brightness is really differ from the truth. I've tried to replace actual_brightness to brightness in the backlight.source, and things started working. Probably actual_brightness is very hardware specific.
Environment:
Linux 6.18.20-1-lts
More things to fix: backlight.widget has wrong bar calculation.
PS: yes, I've applied fix from the #457
/sys/class/backlight/<backlight>/actual_brightness
Show the actual brightness by querying the hardware. Due to implementation differences in hardware this may not match the value in ‘brightness’. For example some hardware may treat blanking differently or have custom power saving features. Userspace should generally use the values in ‘brightness’ to make decisions.
There is a 10% on backlight seeing to prevent accidentally seeing it to
zero and losing visibility. Would be easy to make the lower limit
configurable. …
min_brightness = 5 doesn't work on my side too. Looks like the minimum brightness is set somewhere in system (kernel level, etc, i dont know). I've tried other utilities like light, but it still doesn't work. When I set brightness below 10% with this tool, it shows less than 10%, but visually I see no changes.
Why exactly the brightness below 10% doesn't work in sfwbar? I guess, it's because the setting value happened via DBus call, but reading the value via /sysfs/.../brightness. I've checked, the sfwbar sends brightness values below 10% to the DBus correctly (1%,2%,3%, etc), but in doesn't affect.
Ah yes, indeed, there is a 10% global limit on brightness to prevent
accidental blanking of the screen. You can change it by copying
backlight.source into your configuration directory (i.e. ~/.config/sfwbar)
and changing line 44: Max(10, ...), 10 is the global limit in %, so change
it to whatever value you want. (this is convoluted because it's meant as a
failsafe).
Me and other people use every day 'brightnessctl s 61' (launched with custom in Hyprland), so I don't think any accidental blanking could happen with 5% backlight
brightnessctl s 61
Updated device 'intel_backlight':
Device 'intel_backlight' of class 'backlight':
Current brightness: 61 (7%)
Max brightness: 937
If it's just a matter of setting the global minimum a bit lower, it's not
an issue. I just don't want to set it too close to zero. I updated the
config in git to floor at 5% now.
On 5/19/26 10:52 PM, LBCrion wrote:
*LBCrion* left a comment (LBCrion/sfwbar#462) <https://github.com/LBCrion/sfwbar#462#issuecomment-4491941081>
If it's just a matter of setting the global minimum a bit lower, it's not
an issue. I just don't want to set it too close to zero. I updated the
config in git to floor at 5% now.
On Tue, May 19, 2026 at 10:11 AM maderios ***@***.***> wrote:
> *maderios* left a comment (LBCrion/sfwbar#462)
> <#462 (comment)>
>
> Me and other people use every day 'brightnessctl s 61' (launched with
> custom in Hyprland), so I don't think any accidental blanking could
happen
> with 5% backlight
>
> brightnessctl s 61
> Updated device 'intel_backlight':
> Device 'intel_backlight' of class 'backlight':
> Current brightness: 61 (7%)
> Max brightness: 937
>
>
> —
> Reply to this email directly, view it on GitHub
> <#462 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/
ASHPFFEOZDOWAXLZLVX6IW343QQLVAVCNFSM6AAAAACX3KKNTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOBWGIYDENRXGM>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-
email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?
id=com.github.android&referrer=utm_campaign%3Dnotification-
email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <https://github.com/LBCrion/sfwbar#462#issuecomment-4491941081>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/
AIFPRM3QYBIIYKB7XL7SJD343TCQBAVCNFSM6AAAAACX3KKNTSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOJRHE2DCMBYGE>.
Triage notifications on the go with GitHub Mobile for iOS <https://
apps.apple.com/app/apple-store/id1477376905?ct=notification-
email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/
details?id=com.github.android&referrer=utm_campaign%3Dnotification-
email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Activity
LBCrion commentedon Apr 16, 2026
maderios commentedon Apr 16, 2026
Yes, it seems to be same issue, mouse scroll wheel on widget works for me too.
But i can't get backlight 5%
LBCrion commentedon Apr 16, 2026
telychko commentedon May 17, 2026
Same problem here. After the look around, I noticed that math
actual_brightness / max_brightnessis not working for me.actual_brightnessis really differ from the truth. I've tried to replaceactual_brightnesstobrightnessin thebacklight.source, and things started working. Probablyactual_brightnessis very hardware specific.Environment:
Linux 6.18.20-1-lts
More things to fix:
backlight.widgethas wrong bar calculation.PS: yes, I've applied fix from the #457
Suggested fix:
telychko commentedon May 18, 2026
What I've found in the kernel doc:
LBCrion commentedon May 18, 2026
@telychko, thank you! I applied both changes to the current git.
maderios commentedon May 18, 2026
How to configure a lower limit ? (5% for me)
LBCrion commentedon May 18, 2026
maderios commentedon May 18, 2026
I already use 'min_brightness = 5;' but it doesn't work
telychko commentedon May 18, 2026
min_brightness = 5doesn't work on my side too. Looks like the minimum brightness is set somewhere in system (kernel level, etc, i dont know). I've tried other utilities like light, but it still doesn't work. When I set brightness below 10% with this tool, it shows less than 10%, but visually I see no changes.Why exactly the brightness below 10% doesn't work in sfwbar? I guess, it's because the setting value happened via DBus call, but reading the value via /sysfs/.../brightness. I've checked, the sfwbar sends brightness values below 10% to the DBus correctly (1%,2%,3%, etc), but in doesn't affect.
LBCrion commentedon May 19, 2026
maderios commentedon May 19, 2026
Me and other people use every day 'brightnessctl s 61' (launched with custom in Hyprland), so I don't think any accidental blanking could happen with 5% backlight
LBCrion commentedon May 19, 2026
maderios commentedon May 20, 2026
LBCrion commentedon Nov 18, 2026
I'll close this, as it seems to be resolved. Please feel free to re-open if anything still isn't working as expected.