I think this bug has been introduced in this update (but I could be wrong):
gnome-power-manager (2.19.6-0ubuntu3) gutsy; urgency=low
* GetBrightness returns an int, not an unsigned int
-- Matthew Garrett <email address hidden> Wed, 29 Aug 2007 22:06:03 +0100
When g-p-m tries to read my brightness (before setting what it reads to a higher level), I get:
[gpm_brightness_lcd_init] gpm-brightness-lcd.c:496 (20:49:31): Laptop panel levels: 101
(gnome-power-manager:10254): GLib-GObject-CRITICAL **: g_value_set_uint: assertion `G_VALUE_HOLDS_UINT (value)' failed [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (20:49:31): GetBrightness returned level: 0
I think this bug has been introduced in this update (but I could be wrong):
gnome-power-manager (2.19.6-0ubuntu3) gutsy; urgency=low
* GetBrightness returns an int, not an unsigned int
-- Matthew Garrett <email address hidden> Wed, 29 Aug 2007 22:06:03 +0100
When g-p-m tries to read my brightness (before setting what it reads to a higher level), I get:
[gpm_brightness _lcd_init] gpm-brightness- lcd.c:496 (20:49:31): Laptop panel levels: 101
(gnome- power-manager: 10254): GLib-GObject- CRITICAL **: g_value_set_uint: assertion `G_VALUE_HOLDS_UINT (value)' failed _lcd_get_ hw] gpm-brightness- lcd.c:116 (20:49:31): GetBrightness returned level: 0
[gpm_brightness