GNOME Bugzilla – Bug 782155
Some PCs still turn off the backlight by zero brightness even when the maximum brightness level is less than 100.
Last modified: 2019-03-20 11:42:26 UTC
The minimum brightness of the laptop screen panel may not be realistic sometimes especially when having a problematic screen panel. For example, Dell Precision 5720 AIO only has 9 levels in /sys/class/backlight/intel_backlight/max_brightness because the wrong settings in VBIOS. It is an all-in-one desktop PC and there is no brightness hotkey to control the backlight. When we set 0 to /sys/class/backlight/intel_backlight/brightness, it turns off the panel's backlight and there is no way to brightness up the backlight again so we can only avoid using 0 as the minimum backlight level.
Created attachment 351039 [details] [review] power: Provide a customizable minimum brightness setting I have tested this patch on Fedora 25 with jhbuild and it seems to work fine as what I expected.
Review of attachment 351039 [details] [review]: That's out of the question. See https://bugzilla.gnome.org/show_bug.cgi?id=744278 for how we'd want it to be solved.
I can still reduplicate this issue on Dell Precision 5720 AIO. It only has 9 levels in /sys/class/backlight/intel_backlight/max_brightness because the wrong settings in VBIOS. How can we fix this problem? Any idea?
Created attachment 351052 [details] [review] Avoid using zero brightness by settings.
Review of attachment 351052 [details] [review]: No, this shouldn't need a configuration option. If this requires fixing the kernel, the kernel be fixed.
(In reply to Bastien Nocera from comment #5) > Review of attachment 351052 [details] [review] [review]: > > No, this shouldn't need a configuration option. If this requires fixing the > kernel, the kernel be fixed. Sorry for being dense - what kind of fix do you have in mind?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/331.