GNOME Bugzilla – Bug 698271
Brightness doesn't lower past 95%
Last modified: 2014-04-24 09:56:29 UTC
Brightness control buttons (on the keyboard) in GNOME is broken. Buttons on the keyboard brightness is regulated only within 95-100%. In KDE/XFCE/etc. all works fine. In gnome-control-center screen all works. echo ... > /sys/class/backlight/acpi_video0/brightness works /sys/class/backlight/acpi_video0/max_brightness is 100 RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=922192
*** Bug 698273 has been marked as a duplicate of this bug. ***
it is not entirely clear what you mean by 'regulated only within 95-100%' - are you saying that your screen brightness doesn't go to 100% with the function keys ?
$ cat /sys/class/backlight/acpi_video0/brightness 100 I hold Fn+F8 (decrease backlight) $ cat /sys/class/backlight/acpi_video0/brightness 95 I change backlight in gnome-control-center screen to 50% $ cat /sys/class/backlight/acpi_video0/brightness 50 I hold Fn+F8 (decrease backlight) $ cat /sys/class/backlight/acpi_video0/brightness 15 I hold Fn+F9 (increase backlight) $ cat /sys/class/backlight/acpi_video0/brightness 75 I want to tell that the keyboard shortcuts don't regulate backligt properly (from 0 to 100) (In reply to comment #2) > it is not entirely clear what you mean by 'regulated only within 95-100%' - are > you saying that your screen brightness doesn't go to 100% with the function > keys ?
In Debian with Linux kernel 3.2 max_backlight is 15 and regulation happens normally. Since Linux kernel 3.5 or 3.6 max_backlight is 100 and regulation doesn't work normally. In Fedora I have 3.8.x kernel (In reply to comment #2) > it is not entirely clear what you mean by 'regulated only within 95-100%' - are > you saying that your screen brightness doesn't go to 100% with the function > keys ?
What is necessary still information? (In reply to comment #2) > it is not entirely clear what you mean by 'regulated only within 95-100%' - are > you saying that your screen brightness doesn't go to 100% with the function > keys ?
> I want to tell that the keyboard shortcuts don't regulate backligt properly > (from 0 to 100) I don't understand what this means.
I uploaded video on YouTube. It hope will help to understand a problem better. http://www.youtube.com/watch?v=sKJdu22dM_Y (In reply to comment #6) > > I want to tell that the keyboard shortcuts don't regulate backligt properly > > (from 0 to 100) > > I don't understand what this means.
Got it. The "lower backlight" button doesn't allow going under 95%. It should be going to 90% (as per BRIGHTNESS_STEP_AMOUNT() with 100 values). Looks like a problem in the kernel. Does running this as root work? /usr/libexec/gsd-backlight-helper --set-brightness 90
Yes. All works. (In reply to comment #8) > Got it. The "lower backlight" button doesn't allow going under 95%. It should > be going to 90% (as per BRIGHTNESS_STEP_AMOUNT() with 100 values). > > Looks like a problem in the kernel. > > Does running this as root work? > /usr/libexec/gsd-backlight-helper --set-brightness 90
(In reply to comment #9) > Yes. All works. What does that mean? Does it lower the brightness? What's the output of: /usr/libexec/gsd-backlight-helper --get-brightness ?
Yes. It lower the brightness. # /usr/libexec/gsd-backlight-helper --get-brightness 90 (In reply to comment #10) > (In reply to comment #9) > > Yes. All works. > > What does that mean? Does it lower the brightness? > What's the output of: > /usr/libexec/gsd-backlight-helper --get-brightness > ?
When reproducing the problem, instead of pressing the brightness down button, can you try launching this command a few times in a row and give me the output? gdbus call --session --dest org.gnome.SettingsDaemon.Power --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown Does the same problem happen if you launch this command a few times but waiting a bit between the calls?
I testing in Fedora 18 with gnome 3.6... At the night I will test in Fedora 19 with gnome 3.8. # LANG=en_US.UTF-8 gdbus call --session --dest org.gnome.SettingsDaemon.Power --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Power was not provided by any .service files (In reply to comment #12) > When reproducing the problem, instead of pressing the brightness down button, > can you try launching this command a few times in a row and give me the output? > > gdbus call --session --dest org.gnome.SettingsDaemon.Power --object-path > /org/gnome/SettingsDaemon/Power --method > org.gnome.SettingsDaemon.Power.Screen.StepDown > > Does the same problem happen if you launch this command a few times but waiting > a bit between the calls?
You need to run this as a normal user, not as root. Under GNOME 3.6, it might be "--dest org.gnome.SettingsDaemon" instead of "--dest org.gnome.SettingsDaemon.Power".
$ ./backlight_test.sh Wed Apr 24 19:31:41 MSK 2013 (uint32 95,) Wed Apr 24 19:31:41 MSK 2013 (uint32 95,) Wed Apr 24 19:31:42 MSK 2013 (uint32 95,) Wed Apr 24 19:31:47 MSK 2013 (uint32 95,) Wed Apr 24 19:31:52 MSK 2013 (uint32 95,) My script: #!/bin/sh LANG=en_US.UTF-8 date gdbus call --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown date gdbus call --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown sleep 1s date gdbus call --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown sleep 5s date gdbus call --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown sleep 5s date gdbus call --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown (In reply to comment #14) > You need to run this as a normal user, not as root. > > Under GNOME 3.6, it might be "--dest org.gnome.SettingsDaemon" instead of > "--dest org.gnome.SettingsDaemon.Power".
What's the output of xbacklight on your system (it's in the xbacklight package)? If it returns nothing, it narrows down the problem to 10 lines of code in the power plugin of gnome-settings-daemon, but it's really not obvious what could be broken there.
# /usr/libexec/gsd-backlight-helper --get-brightness 95 # xbacklight 100.000000 (In reply to comment #16) > What's the output of xbacklight on your system (it's in the xbacklight > package)? > > If it returns nothing, it narrows down the problem to 10 lines of code in the > power plugin of gnome-settings-daemon, but it's really not obvious what could > be broken there.
What hardware is this? It looks like the graphics driver is broken...
Lenovo ThinkPad X230 i7-3520m ( HD 4000 ) (In reply to comment #18) > What hardware is this? It looks like the graphics driver is broken...
In ThinkPad T430 this bug present. I add my friend in CC list with this notebook. (In reply to comment #18) > What hardware is this? It looks like the graphics driver is broken...
> It looks like the graphics driver is broken... But in KDE/XFCE/etc. all works ! (In reply to comment #18) > What hardware is this? It looks like the graphics driver is broken...
My friend has tested this bug in GNOME and KDE on ThinkPad T430 Please, watch this video. http://www.youtube.com/watch?v=WiH1dZ97090 (In reply to comment #18) > What hardware is this? It looks like the graphics driver is broken...
(In reply to comment #21) > > It looks like the graphics driver is broken... > But in KDE/XFCE/etc. all works ! Probably because they don't use the backlight provided in the X driver. > (In reply to comment #18) > > What hardware is this? It looks like the graphics driver is broken...
Do you see any errors in /var/log/Xorg.0.log (or similarly named files, not sure which one is currently used on your system).
(In reply to comment #23) > (In reply to comment #21) > > > It looks like the graphics driver is broken... > > But in KDE/XFCE/etc. all works ! > > Probably because they don't use the backlight provided in the X driver. > > > (In reply to comment #18) > > > What hardware is this? It looks like the graphics driver is broken... huh. I'm sorry. I didn't know. (In reply to comment #24) > Do you see any errors in /var/log/Xorg.0.log (or similarly named files, not > sure which one is currently used on your system). $ egrep -w '(WW)|(EE)' /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 43.435] (WW) Falling back to old probe method for vesa [ 43.435] (WW) Falling back to old probe method for modesetting [ 43.435] (WW) Falling back to old probe method for fbdev
Created attachment 242403 [details] Xorg.0.log for #698271
Ajax (https://fedoraproject.org/wiki/User:Ajax) said yesterday that the some problems with backlight are fixed in the intel-gfx. (In reply to comment #18) > What hardware is this? It looks like the graphics driver is broken...
(In reply to comment #27) > Ajax (https://fedoraproject.org/wiki/User:Ajax) said yesterday that the some > problems with backlight are fixed in the intel-gfx. Ajax actually said that it was a bug in the intel-gfx driver, not that it was fixed. You should go ahead and file a bug against the intel-gfx driver as per: https://01.org/linuxgraphics/documentation/how-report-bugs-0
(In reply to comment #28) > (In reply to comment #27) > > Ajax (https://fedoraproject.org/wiki/User:Ajax) said yesterday that the some > > problems with backlight are fixed in the intel-gfx. > > Ajax actually said that it was a bug in the intel-gfx driver, not that it was > fixed. > > You should go ahead and file a bug against the intel-gfx driver as per: > https://01.org/linuxgraphics/documentation/how-report-bugs-0 I created bug: https://bugs.freedesktop.org/show_bug.cgi?id=63931 Thanks you very much =)
Created attachment 242640 [details] I tested again and was sent to a gnome I tested again and was sent to a gnome (https://bugzilla.kernel.org/show_bug.cgi?id=57131)
Hi Bastien, According to Igor's test report: [root@brain-ThinkPad-X230 acpi_video0]# cat max_brightness 100 [root@brain-ThinkPad-X230 acpi_video0]# cat brightness 100 [root@brain-ThinkPad-X230 acpi_video0]# xbacklight 100.000000 [root@brain-ThinkPad-X230 acpi_video0]# /usr/libexec/gsd-backlight-helper --get-brightness 100 [root@brain-ThinkPad-X230 acpi_video0]# /usr/libexec/gsd-backlight-helper --set-brightness 90 [root@brain-ThinkPad-X230 acpi_video0]# /usr/libexec/gsd-backlight-helper --get-brightness 90 [root@brain-ThinkPad-X230 acpi_video0]# xbacklight 90.000000 [root@brain-ThinkPad-X230 acpi_video0]# cat brightness 90 [brain@brain-ThinkPad-X230 acpi_video0]$ gdbus call --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/Power --method org.gnome.SettingsDaemon.Power.Screen.StepDown (uint32 85,) [root@brain-ThinkPad-X230 acpi_video0]# xbacklight 90.000000 [root@brain-ThinkPad-X230 acpi_video0]# cat brightness 90 It looks like the gdbus call doesn't have an effect. Igor said that manually change the backlight level through the acpi video interface works(with echo).
1) You didn't test whether changing the backlight through xbacklight worked 2) gsd-backlight-helper isn't used or called in GNOME if the driver offers XRandR backlight support Run: xbacklight -dec 5 and then: xbacklight should show whether changing the brightness through the backlight interface works.
(In reply to comment #32) > 1) You didn't test whether changing the backlight through xbacklight worked > 2) gsd-backlight-helper isn't used or called in GNOME if the driver offers > XRandR backlight support > > Run: > xbacklight -dec 5 > and then: > xbacklight > > should show whether changing the brightness through the backlight interface > works. huh! $ xbacklight 100.000000 $ xbacklight -dec 5 $ xbacklight 100.000000 $ xbacklight -dec 10 $ xbacklight 90.000000 $ xbacklight -inc 5 $ xbacklight 90.000000 $ xbacklight -inc 10 $ xbacklight 100.000000 and backlight lower...
(In reply to comment #33) > (In reply to comment #32) > > 1) You didn't test whether changing the backlight through xbacklight worked > > 2) gsd-backlight-helper isn't used or called in GNOME if the driver offers > > XRandR backlight support > > > > Run: > > xbacklight -dec 5 > > and then: > > xbacklight > > > > should show whether changing the brightness through the backlight interface > > works. > huh! > $ xbacklight > 100.000000 > $ xbacklight -dec 5 > $ xbacklight > 100.000000 > $ xbacklight -dec 10 > $ xbacklight > 90.000000 > $ xbacklight -inc 5 > $ xbacklight > 90.000000 > $ xbacklight -inc 10 > $ xbacklight > 100.000000 > and backlight lower... sorry. real backlight is equal to that shows xbacklight
(In reply to comment #32) > 1) You didn't test whether changing the backlight through xbacklight worked > 2) gsd-backlight-helper isn't used or called in GNOME if the driver offers > XRandR backlight support > > Run: > xbacklight -dec 5 > and then: > xbacklight > > should show whether changing the brightness through the backlight interface > works. $ xbacklight -set 99 $ xbacklight 100.000000 $ xbacklight -set 95 $ xbacklight 100.000000 $ xbacklight -set 91 $ xbacklight 100.000000
If xbacklight shows the same symptons as gnome-settings-daemon, I'm afraid that's about how far I can go to fix this problem. Given that setting the backlight directly (through sysfs) to values like 95% works but doesn't through xbacklight, either xbacklight is broken, or the driver is doing something wrong. Aron, let me know if I'm wrong here.
(In reply to comment #36) > If xbacklight shows the same symptons as gnome-settings-daemon, I'm afraid > that's about how far I can go to fix this problem. > > Given that setting the backlight directly (through sysfs) to values like 95% > works but doesn't through xbacklight, either xbacklight is broken, or the > driver is doing something wrong. > > Aron, let me know if I'm wrong here. I don't know anything about xbacklight :-) Care to explain what does "driver is doing something wrong" mean here? Is it the xorg driver providing information for xbacklight?
(In reply to comment #37) > (In reply to comment #36) > > If xbacklight shows the same symptons as gnome-settings-daemon, I'm afraid > > that's about how far I can go to fix this problem. > > > > Given that setting the backlight directly (through sysfs) to values like 95% > > works but doesn't through xbacklight, either xbacklight is broken, or the > > driver is doing something wrong. > > > > Aron, let me know if I'm wrong here. > > I don't know anything about xbacklight :-) > Care to explain what does "driver is doing something wrong" mean here? Is it > the xorg driver providing information for xbacklight? Aaron Lu, see this comment please. https://bugs.freedesktop.org/show_bug.cgi?id=63931#c11
I found bug in BZ Kernel! https://bugzilla.kernel.org/show_bug.cgi?id=51231 https://patchwork.kernel.org/patch/2124861/
*** Bug 708618 has been marked as a duplicate of this bug. ***
*** Bug 728354 has been marked as a duplicate of this bug. ***