Activity log for bug #207473

Date Who What changed Old value New value Message
2008-03-27 00:23:40 sonicated bug added bug
2008-03-27 00:37:28 sonicated description Binary package hint: gnome-power-manager I have a fresh installation of Hardy with the latest updates installed on a Dell Inspiron 6400 laptop. The brightness settings (Fn+Up/Down) work although they seem to skip a level each time. '/proc/acpi/video/VID/LCD/brightness' tells me that it supports brightness levels 12, 24, 36, 48, 60, 72, 84 and 100. Without gnome-power-manager running pressing Fn+Up will transition up into each level and back down again smoothly. When gnome-power-manager is running increasing the brightness from 12 I can only get levels 36, 60, 84 and 100. Decreasing the levels from 100 I only get 72, 48, 24 and 12. Running gnome-power-manager with the verbose option shows that when I press the brightness-up button once it is recorded twice. I ran gnome-power-manager in a debugger thinking it was a timing issue and it still happened. I have included the output from pressing the brightness-up button (Fn+Up) once below. This only happens when gnome-power-manager is running and did not happen using Feisty. I have looked at the code and I cannot see why the button event is triggered twice, I don't have any experience of the code but if you can give me any ideas of where to start I can look into this myself. Thanks! [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48): Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 0 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 1 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (14) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48): Need to display backlight feedback value 14 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.140000 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 1 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48): emitting brightness-changed : 14 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48): Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 1 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 2 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (28) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48): Need to display backlight feedback value 28 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.280000 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 2 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48): emitting brightness-changed : 28 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [gpm_refcount_auto_decrement] gpm-refcount.c:77 (00:11:50): refcount now: 1 [gpm_refcount_auto_decrement] gpm-refcount.c:74 (00:11:50): zero, so sending REFCOUNT_ZERO [gpm_feedback_close_window] gpm-feedback-widget.c:134 (00:11:50): Closing feedback widget Binary package hint: gnome-power-manager I have a fresh installation of Hardy with the latest updates installed on a Dell Inspiron 6400 laptop. The brightness settings (Fn+Up/Down) work although they seem to skip a level each time. '/proc/acpi/video/VID/LCD/brightness' tells me that it supports brightness levels 12, 24, 36, 48, 60, 72, 84 and 100. Without gnome-power-manager running pressing Fn+Up will transition up into each level and back down again smoothly. When gnome-power-manager is running increasing the brightness from 12 I can only get levels 36, 60, 84 and 100. Decreasing the levels from 100 I only get 72, 48, 24 and 12. Running gnome-power-manager with the verbose option shows that when I press the brightness-up button once it is recorded twice. I ran gnome-power-manager in a debugger thinking it was a timing issue and it still happened. I have included the output from pressing the brightness-up button (Fn+Up) once below. This only happens when gnome-power-manager is running and did not happen using Feisty. I have looked at the code and I cannot see why the button event is triggered twice, I don't have any experience of the code but if you can give me any ideas of where to start I can try to look into this myself. Thanks! [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48): Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 0 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 1 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (14) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48): Need to display backlight feedback value 14 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.140000 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 1 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48): emitting brightness-changed : 14 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [hal_device_condition_cb] gpm-button.c:391 (00:11:48): condition=ButtonPressed, details=brightness-up [emit_button_pressed] gpm-button.c:335 (00:11:48): emitting button-pressed : brightness-up [button_pressed_cb] gpm-manager.c:999 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-srv-screensaver.c:167 (00:11:48): Button press event type=brightness-up [button_pressed_cb] gpm-backlight.c:563 (00:11:48): Button press event type=brightness-up [gpm_brightness_lcd_get_hw] gpm-brightness-lcd.c:116 (00:11:48): GetBrightness returned level: 1 [gpm_brightness_lcd_set_hw] gpm-brightness-lcd.c:155 (00:11:48): Setting 2 of 7 [gpm_brightness_lcd_up] gpm-brightness-lcd.c:362 (00:11:48): emitting brightness-changed (28) [brightness_changed_cb] gpm-backlight.c:755 (00:11:48): Need to display backlight feedback value 28 [gpm_feedback_display_value] gpm-feedback-widget.c:144 (00:11:48): Displaying 0.280000 on feedback widget [gpm_refcount_add] gpm-refcount.c:100 (00:11:48): refcount now: 2 [gpm_refcount_add] gpm-refcount.c:101 (00:11:48): non zero, so sending REFCOUNT_ADDED [brightness_changed_cb] gpm-backlight.c:759 (00:11:48): emitting brightness-changed : 28 [button_pressed_cb] gpm-info.c:698 (00:11:48): Button press event type=brightness-up [gpm_refcount_auto_decrement] gpm-refcount.c:77 (00:11:50): refcount now: 1 [gpm_refcount_auto_decrement] gpm-refcount.c:74 (00:11:50): zero, so sending REFCOUNT_ZERO [gpm_feedback_close_window] gpm-feedback-widget.c:134 (00:11:50): Closing feedback widget
2008-04-11 16:12:15 Adam bug added attachment 'unnamed' (unnamed)
2008-04-16 05:31:58 Steve Langasek hal: importance Undecided Medium
2008-04-27 23:37:11 Juan Pablo Salazar Bertín bug added attachment 'lshal.txt' (lshal.txt)
2008-04-30 04:31:33 Juan Pablo Salazar Bertín hal: status New Confirmed
2008-05-05 21:30:30 Andreas Wenning bug assigned to kde-guidance (Ubuntu)
2008-05-05 21:32:40 Andreas Wenning kde-guidance: status New Confirmed
2008-05-05 21:32:40 Andreas Wenning kde-guidance: assignee andreas-wenning
2008-05-12 03:03:15 Juan Pablo Salazar Bertín bug added attachment 'lshal-video_blacklisted.txt' (lshal-video_blacklisted.txt)
2008-05-12 14:50:06 Andreas Wenning bug added attachment 'kde-guidance_0.8.0svn20080103-0ubuntu16.1.debdiff' (kde-guidance_0.8.0svn20080103-0ubuntu16.1.debdiff)
2008-05-12 15:01:32 Scott Kitterman kde-guidance: importance Undecided Medium
2008-05-12 15:02:11 Scott Kitterman kde-guidance: importance Undecided Medium
2008-05-12 15:02:11 Scott Kitterman kde-guidance: status New Confirmed
2008-05-12 15:02:11 Scott Kitterman kde-guidance: milestone ubuntu-8.04.1
2008-05-12 16:00:10 Launchpad Janitor kde-guidance: status Confirmed Fix Released
2008-06-11 02:57:12 Frankie83 bug added attachment 'unnamed' (unnamed)
2008-06-19 21:43:21 Hinrich hal: status New Confirmed
2008-06-20 06:55:46 Steve Langasek kde-guidance: status Confirmed Fix Committed
2008-06-20 07:13:19 Steve Langasek kde-guidance: status Fix Committed Fix Released
2008-10-20 07:11:07 Mario Limonciello hal: status Confirmed Invalid
2008-10-20 07:11:07 Mario Limonciello hal: statusexplanation this is actually caused by a BIOS bug/kernel bug (depends who you talk to). It's because the BIOS has tables in the DSDT to represent the possible different video cards that would ship with the box (UMA or discrete). There is a fix available upstream, but it causes regressions on other machines. It will need to be tracked until it's ready.
2008-10-20 07:11:24 Mario Limonciello hal: status Confirmed Invalid
2008-10-20 07:11:24 Mario Limonciello hal: statusexplanation The latest updates didn't fix anything for me either (8.04, GNOME, Dell XPS M1330, Intel graphics)
2008-10-20 07:11:49 Mario Limonciello bug assigned to linux
2008-10-20 07:12:09 Mario Limonciello bug assigned to linux (Ubuntu)
2008-10-20 07:12:44 Mario Limonciello linux: status New Confirmed
2008-10-20 07:12:44 Mario Limonciello linux: importance Undecided Low
2008-10-20 07:12:44 Mario Limonciello linux: statusexplanation
2008-10-20 07:13:00 Mario Limonciello linux: status New Confirmed
2008-10-20 07:13:00 Mario Limonciello linux: importance Undecided Low
2008-10-20 07:13:00 Mario Limonciello linux: statusexplanation
2008-10-20 07:46:34 Bug Watch Updater linux: status Unknown Confirmed
2008-11-17 11:18:08 Bug Watch Updater linux: status Confirmed Fix Released
2009-04-24 00:25:58 Steve Langasek summary Screen brightness double level changes Screen brightness double level changes on Dell laptops
2009-04-24 00:37:14 Steve Langasek linux (Ubuntu): status Confirmed Fix Released
2009-04-24 14:46:14 Bruce Cowan removed subscriber Bruce Cowan
2009-08-15 09:26:25 Sandro Mani removed subscriber Sandro Mani
2009-08-21 01:10:29 Launchpad Janitor branch linked lp:ubuntu/hardy-proposed/kde-guidance
2009-08-21 01:11:07 Launchpad Janitor branch linked lp:ubuntu/intrepid/kde-guidance
2009-10-30 18:59:24 Steve Langasek linux (Ubuntu): status Fix Released Confirmed
2009-10-30 19:34:00 Pavel Malyshev attachment added dmesg.log http://launchpadlibrarian.net/34715326/dmesg.log
2009-10-30 19:35:23 Pavel Malyshev attachment added xkbcomp.txt http://launchpadlibrarian.net/34715414/xkbcomp.txt
2009-10-30 19:36:46 Pavel Malyshev attachment added lsinput.log http://launchpadlibrarian.net/34715531/lsinput.log
2009-10-30 19:38:02 Pavel Malyshev attachment added udev-db.txt http://launchpadlibrarian.net/34715620/udev-db.txt
2009-11-02 16:07:16 Daniel Hurtado removed subscriber Daniel Hurtado
2009-11-03 01:43:14 Adam removed subscriber Adam
2009-11-03 06:34:34 Pavel Malyshev attachment added lshal.txt http://launchpadlibrarian.net/35006997/lshal.txt
2009-11-03 12:41:51 Amir Khosroshahi removed subscriber Amir Khosroshahi
2009-11-03 23:09:52 Steve Langasek linux (Ubuntu): importance Low Medium
2009-11-03 23:09:52 Steve Langasek linux (Ubuntu): status Confirmed Triaged
2009-11-03 23:09:52 Steve Langasek linux (Ubuntu): assignee Ubuntu Kernel Team (ubuntu-kernel-team)
2009-11-17 18:45:08 Ubuntu QA Website tags verification-done iso-testing verification-done
2010-02-05 18:35:17 Jeremy Foshee linux (Ubuntu): status Triaged Fix Released
2010-03-31 21:06:29 Michael Rooney removed subscriber Michael Rooney
2010-12-25 08:16:44 Eric bug added subscriber Eric
2011-02-04 08:43:47 Mikael Gerdin removed subscriber Mikael Gerdin
2011-02-04 10:25:50 Bug Watch Updater linux: importance Unknown Medium
2011-06-06 16:35:01 Svetoslav Popov bug added subscriber Svetoslav Popov
2011-08-01 18:01:47 gl bug added subscriber gl
2012-01-10 05:30:06 P Liu bug added subscriber P Liu
2012-01-23 04:22:01 Daniel Ansari bug added subscriber Daniel Ansari
2012-03-15 13:58:18 Svetoslav Popov removed subscriber Svetoslav Popov
2012-03-31 23:20:38 Adam Porter bug added subscriber Adam Porter
2012-09-05 21:34:54 Michael Rodríguez-Torrent bug added subscriber Michael Rodríguez-Torrent
2012-11-06 07:31:16 mihai.ile bug added subscriber mihai007
2012-11-08 00:49:50 Steven Nichols removed subscriber Steven Nichols
2013-08-18 17:35:28 Julian Wiedmann linux (Ubuntu Hardy): status Confirmed Invalid
2014-04-23 10:42:46 Guido Conaldi removed subscriber Guido Conaldi
2015-08-30 10:30:33 Pavel Malyshev bug watch added https://bugzilla.redhat.com/show_bug.cgi?id=1141525
2015-09-01 06:12:51 Andreas Peer removed subscriber Andreas Peer