Description of problem: When I press the keyboard backlight on/off keys, a little icon comes up on the screen but the backlight never actually turns on (the progress bar widget also remains empty). I'm not sure if this is because the ambient light sensor reading is incorrect, as I know on OS X the backlight won't turn on unless it's dark and the readings from the sensor in Fedora 10 seem to be incorrect (see comment 1 in bug 470044) Version-Release number of selected component (if applicable): hal-0.5.12-12.20081027git.fc10.x86_64 gnome-power-manager-2.24.1-3.fc10.x86_64 kernel-2.6.27.5-117.fc10.x86_64 How reproducible: Always Steps to Reproduce: 1. Login 2. Press the F5/F6 keys Actual results: A icon for the keyboard brightness appears, but the backlight never turns on and the progress bar does not advance from its initial position no matter how many times F6 is pressed Expected results: Keyboard backlight turns on Additional info:
This is a symptom of the D-Bus breakage that prominently affected PackageKit earlier. Updating to the D-Bus package now in Koji or the original from F10 corrects this issue and several D-Bus related maladies. It is very disappointing that such a package ever hit the stable updates repo, let's hope Red Hat gets it together with the testing. : (
It doesn't seem to be the DBus issue - the light sensor is still erratic for the screen backlight and the keyboard LED's won't turn on either.
Same story with Fedora 11 Alpha - pressing the keyboard backlight keys produces an indicator on-screen, but the progressbar won't move from 0% and the LEDs don't turn on.
First, please try the latest kernel, say 2.6.30. please also attach the acpidump output of your laptop, using the latest pmtools at http://www.lesswatts.org/projects/acpi/utilities.php
Created attachment 356601 [details] acpidump while running kernel 2.6.31 Here you go, I ran this running kernel 2.6.31 from a F12 Koji build. Also using the latest pmtools package from the Fedora 11 repos.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora 'version' of '10'. 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 prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
For me the keyboard backlight adjusting keys on my macbook pro are still not working. Not even the progressbar comes up - the keys are just dead. I can turn on the backlight by doing it manually (/sys/devices/platform/applesmc.768/leds/brightness and echo 200 in there, for example). This is on FC12 and kernel: 2.6.31.5-127.fc12.i686.PAE I am also attaching the acpidump output based on the discussion above.
Created attachment 375357 [details] acpi dump on .6.31.5-127.fc12.i686.PAE
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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. Thank you for reporting this bug and we are sorry it could not be fixed.