gutsy: g-p-m 2.19.6-0ubuntu4 breaks brightness control

Bug #136346 reported by Nikolaus Filus
42
Affects Status Importance Assigned to Milestone
gnome-power
Fix Released
Medium
gnome-power-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

gnome-power-manager 2.19.6-0ubuntu4 introduces a regression from 2.19.6-0ubuntu2
as it breaks brightness control. On my Samsung P35 when g-p-m is running it sets the brightness
to minimum and I'm no longer able to change it. Every keypress of brightness-up goes 1 level up and
down, staying the same level. Downgrading back to 2.19.6-0ubuntu2 makes it work again.

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Same problem here, attaching a debug when pressing the brightness button 3 times

Nicolò Chieffo (yelo3)
Changed in gnome-power-manager:
status: New → Confirmed
Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

Bug #136693 and its duplicate have been added as duplicates of this bug. You can find more info about this issue there.

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

The patch applied in g-p-m version 2.19.6-0ubuntu3 fixes bug #130274, which is MacBooks users getting the same behaviour as us, but at the same time it breaks g-p-m for other users.

I think a better thing to do is to replicate what is being done upstream <http://news.gmane.org/find-root.php?group=gmane.comp.freedesktop.hal&article=8454>.

Changed in gnome-power:
status: Unknown → New
Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

This has been fixed for me with hal version 0.5.9.1-1ubuntu7.
Please confirm.

Revision history for this message
elyk (elyk53) wrote :

Fixed for me too. Thanks

Revision history for this message
Alexey Borzenkov (snaury) wrote :

Fix confirmed, thanks a lot!

Matthew Garrett (mjg59)
Changed in gnome-power-manager:
status: Confirmed → Fix Released
Revision history for this message
junk123 (junk123-deactivatedaccount-deactivatedaccount) wrote :

Bug seems to be back, anyone else?

Revision history for this message
elyk (elyk53) wrote :

I've got a similar bug occurring again, but it's not exactly the same - the down key increments properly one step at at time now, whereas before one press would send the brightness all the way down to the lowest setting. But the up key still is displaying the same behavior

Revision history for this message
elyk (elyk53) wrote :

Bug has returned, so fix is no longer valid

Changed in gnome-power-manager:
status: Fix Released → New
Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

It's a new bug, there are some reports like bug #140839 and bug #140572, and probably bug #117327.

In my case, this time g-p-m is using 6 as the unit to add/subtract to current brightness level. According to acpi, my brightness possible levels are: 12 24 36 48 60 72 84 100. So, if I'm at 100, then g-p-m subtract 6 and sets 94, I end up at 84 (the next level below), but when g-p-m adds 6 to 84 and sets 90, I'm still at 84, since I need 100 to be at the next level.

Revision history for this message
Juan Pablo Salazar Bertín (snifer) wrote :

Bug has not returned, it's a different bug.

Changed in gnome-power-manager:
status: New → Fix Released
Revision history for this message
Nikolaus Filus (nfilus) wrote :

g-p-m is very broken in gutsy - no matter what version.
Since I upgraded to gutsy, there are a lot of regressions I see, which seem to
be confirmed by a lot of people.
FYI: Currently I'm using
  hal 0.5.9.1-1ubuntu8
  gnome-power-manager 2.20.0-ubuntu1

For my above reported bug I had to delete the gconf subtree of g-p-m to get the
fix working during an ongoing session. This issue has gone away, but ...

 - "dim display when idle" IS OFF, but I see brightness go down to 0% and back to 100% when idle
 - on first login after startup g-p-m consumes 100% CPU and my display
   is rapidly flashing showing a brightness around 50%.

... and most annoying is, that after killing g-p-m for restoring a sane state, I can't logout or suspend
anymore, as the quit action in Gnome seems to rely on a running g-p-m.

The state gnome-power-manager is unusable and there are 252 bugs open currently. How can such a piece
of broken software be released?

Revision history for this message
junk123 (junk123-deactivatedaccount-deactivatedaccount) wrote :

Anyone know the status on this its still not working

Revision history for this message
Jarrod Henry (jarrodhenry) wrote :

I think I am seeing a duplicate of this bug as well. When off AC, I adjust the brightness, however, the "Dim to" takes over and down adjusts my brightness. This happens irregularly, though.. sometimes it stays bright the whole time.. sometimes it goes down.. sometimes it goes to a lower point than what the "dimmer" was set to.

Machine is a Dell Inspiron E1405.

Revision history for this message
Boris Kairat (boris-g-kairat) wrote :

Confirm: On the first login after startup g-p-m consumes 100% CPU and my display is rapidly flashing (going up and down) showing a brightness around 50%.
Is this problem solved yet?
I am using a P35III with gpm: 2.20.0-0ubuntu6.

Revision history for this message
Boris Kairat (boris-g-kairat) wrote :

I had a clean install an hour ago.
Problem still exists.

Version: 7.10 (gutsy)
Kernel Linux 2.6.22-14-rt
Gnome 2.20.0

I NEED A FIX! PLEASE! :-)

Revision history for this message
kpictjl (todlarson) wrote :

Problem confirmed. Gnome Brightness applet says "Cannot get laptop panel brightness."
gnome-power-manager v. 2.20.0
kernel: 2.6.22.14-generic
Ubuntu 7.10

Changed in gnome-power:
status: New → Fix Released
Revision history for this message
Jan Hlodan (wewek) wrote :

Ubuntu 9.04 32-bit
2.6.28-11-generic

The issue still persists. The display is flashing and power-manager doesn't work correctly - it changes brightness into darkness sometimes.
Also "func" + "F10/F11" doesn't work.

Lenovo 3000 C200

Changed in gnome-power:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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