Red Hat Bugzilla – Bug 1026090
brightness keys won't step up or down
Last modified: 2015-06-29 08:47:56 EDT
Description of problem:
The brightness keys on my Lenovo T60 do not work with Gnome 3.10 on Fedora 20. They worked fine with Gnome 3.8 on Fedora 19. Dragging the slider does work, however.
Apparently this is due to a bug calculating the brightness steps with systems where max_brightness is less than 10. The T60 has a max of 7:
$ cat /sys/class/backlight/acpi_video0/max_brightness
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. hit Fn+Home (brightness up) or Fn+End (brightness down) on Lenovo T60
the OSD pops up, but the brightness does not change
brightness goes up/down as requested
The same here with Laptop Fujitsu Lifebook E8420
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Fedora 20 beta, kernel 3.11.9
[root@vaio backlight]# lspci -nn | grep VGA
00:02.0 VGA compatible controller : Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
Sony Vaio BZ12XN
Same issue on Asus Zenbook Prime UX31A and Acer Aspire One 756.
I tried rhughes' Gnome 3.12 build for Fedora 20 and the brightness keys work again.
*** Bug 1117780 has been marked as a duplicate of this bug. ***
This bug affected my system, and I want to note that when I first encountered it, the brightness keys would not work at all, but gnome would catch the keystrokes and show an onscreen-display of the brightness control slider (it just wouldn't move).
After a later update, it seems now that the kernel is catching the keystrokes, because brightness adjustment keys do work now, but it's happening independently of gnome's adjuster (works the same on the virtual console and during boot).
dmesg shows my kernel setting the brightness with thinkpad_acpi. Display is using radeon kernel modesetting.
Ideally gnome would be in sync with keyboard-based adjustment and show the OCD accordingly, like how sound volume adjustment is currently working.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.