Disyncronisation with current brightness settings and g-p-m

Bug #140018 reported by kimus
10
Affects Status Importance Assigned to Milestone
gnome-power
Invalid
Unknown
gnome-power-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

When my laptop is on battery power g-p-m changes brightness to the the value it's configured in 'Dim display brightness by:' (i.e.: 50%)

But if I change the brightness with the laptop Fn-Keys/Hotkeys, let's say 25%, it's not synchronized with g-p-m.

The following 'bugs' occur:
- When the laptop is idle it dims the display. But when I move the mouse the brightness level is changed to the value configured in g-p-m (50%) and not the custom (25%), and the last, that I did with the laptop Fn-Keys/Hotkeys;
- When I open the preferences dialog from the g-p-m applet the brightness level is also changed like I mentioned above;

Revision history for this message
Kyle Rankin (greenfly-greenfly) wrote :

I also see this issue and I notice that /sys/class/backlight/XXX/brightness is modified both by g-p-m and by the Fn-keys on my laptop so it doesn't appear to be a situation where one is out of sync with the other. A simple way to reproduce this bug:

1. Set battery mode in g-p-m so that backlight is less than 100% when on battery (lets say 25%), and set backlight to dim when idle.

2. Set laptop to run on battery power so backlight dims (in this example to 25%).

3. Use Fn keys to change backlight back to 100%.

4. Wait for idle timeout to kick in and dim backlight completely.

5. Move the mouse to wake up from idle. Backlight will be set to 25% or whatever was set in g-p-m, not the 100% it was set to before idle.

So basically it seems like g-p-m refers to its configured backlight setting when resuming from idle instead of storing the current backlight setting before going idle so it can then restore to that value.

Revision history for this message
Richard Harding (rharding) wrote :

+1 here in up to date gutsy installation

Revision history for this message
Jorge Castro (jorge) wrote :

Confirming.

Changed in gnome-power-manager:
status: New → Confirmed
Changed in gnome-power:
status: Unknown → New
Revision history for this message
Rubin (rubin) wrote :

confirmed with gutsy here. Thinkpad T61.

Revision history for this message
rborovyk (rborovyk) wrote :

This bug is duplicate of the https://bugs.launchpad.net/ubuntu/+bug/131885.
Also in the GNOME bug tracking list: http://bugzilla.gnome.org/show_bug.cgi?id=478128, status: unconfirmed.

I wonder how we can push guys to raise bug's importance :-?

Changed in gnome-power:
status: New → Confirmed
Changed in gnome-power:
status: Confirmed → 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.