[intrepid] screen brightness keys act very slowly

Bug #301744 reported by Marius Gedminas
4
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When I press Fn+Home on my Lenovo ThinkPad T61, I expect the brightness to go up a step, and I expect the OSD to show that change.

What actually happens, is that the brightness goes up a step, the OSD pops up, and then there's a pause of exactly 1 second, after which the brightness goes up another step and the OSD hides. If I hit Fn-Home a few times, there's a 1 second pause between each step, which makes it rather irritating when you want to go up from 50% to 100% or back. Fn-End, which reduces the brightness, has the same delay.

This is a regression since Hardy, where the volume keys worked fine with no pauses.

It could be a duplicate of #286102, except that I don't see the OSD reverting to a previous brightness level, and I haven't seen this bug in Hardy.

Here's the other information requested in https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch:

mg@platonas:~ $ sudo dmidecode -s system-manufacturer
LENOVO
mg@platonas:~ $ sudo dmidecode -s system-product-name
646655G
mg@platonas:~ $ sudo dmidecode -s system-version
ThinkPad T61

The key that Fn-Home sends is XF86MonBrightnessUp, according to GNOME key bindings preferences, and it appears after that 1 second pause. (Fn-End sends XF86MonBrightnessDown). /var/log/acpid doesn't show any ACPI events being sent when I press those keys.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please attach the resulting log file of: gnome-power-bugreport.sh &> gpm.log to the report? You might also want to take a look to the Debugging instructions located at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager for submit any other logs related to your problem.Thanks in advance.

Changed in gnome-power-manager:
status: New → Incomplete
Revision history for this message
Marius Gedminas (mgedmin) wrote :
Revision history for this message
Boniek (boniek12p) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Marius Gedminas (mgedmin) wrote :

Thanks for the reminder; the issue is fixed in Jaunty.

Revision history for this message
Boniek (boniek12p) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.