[Bug 72028] Throttle status not cleared
André Cruz
andre at cabine.org
Thu Nov 16 11:23:27 UTC 2006
Public bug reported:
Binary package hint: gnome-screensaver
After running gnome-screensaver for some time, the theme does not start
when the screensaver activates. It complains that it is throttled but
whatever throttled the screensaver is long gone. Here are the relevant
parts of the screensaver log:
andre at huge:~/gnome-screensaver$ cat ../screensaver.log |grep -i throttle
[listener_add_ref_entry] gs-listener-dbus.c:657 (13:49:55): adding throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (13:49:55): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (13:49:55): throttler: Power Manager for reason: Display power management activated
[gs_listener_set_throttle] gs-listener-dbus.c:377 (13:49:55): Changing throttle status: 1
[listener_remove_ref_entry] gs-listener-dbus.c:682 (14:49:16): removing throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (14:49:16): Checking for throttle
[gs_listener_set_throttle] gs-listener-dbus.c:377 (14:49:16): Changing throttle status: 0
[listener_add_ref_entry] gs-listener-dbus.c:657 (18:46:02): adding throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (18:46:02): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (18:46:02): throttler: Power Manager for reason: Display power management activated
[gs_listener_set_throttle] gs-listener-dbus.c:377 (18:46:02): Changing throttle status: 1
[listener_add_ref_entry] gs-listener-dbus.c:657 (19:46:02): adding throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (19:46:02): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (19:46:02): throttler: Power Manager for reason: Display power management activated
[list_ref_entry] gs-listener-dbus.c:316 (19:46:02): throttler: Power Manager for reason: Display power management activated
[listener_remove_ref_entry] gs-listener-dbus.c:682 (08:00:02): removing throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (08:00:02): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (08:00:02): throttler: Power Manager for reason: Display power management activated
[listener_add_ref_entry] gs-listener-dbus.c:657 (08:30:04): adding throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (08:30:04): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (08:30:04): throttler: Power Manager for reason: Display power management activated
[list_ref_entry] gs-listener-dbus.c:316 (08:30:04): throttler: Power Manager for reason: Display power management activated
[listener_remove_ref_entry] gs-listener-dbus.c:682 (08:33:37): removing throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (08:33:37): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (08:33:37): throttler: Power Manager for reason: Display power management activated
[listener_add_ref_entry] gs-listener-dbus.c:657 (09:03:37): adding throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (09:03:37): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (09:03:37): throttler: Power Manager for reason: Display power management activated
[list_ref_entry] gs-listener-dbus.c:316 (09:03:37): throttler: Power Manager for reason: Display power management activated
[listener_remove_ref_entry] gs-listener-dbus.c:682 (09:19:41): removing throttler from Power Manager for reason 'Display power management activated' on connection :1.6
[listener_check_throttle] gs-listener-dbus.c:390 (09:19:41): Checking for throttle
[list_ref_entry] gs-listener-dbus.c:316 (09:19:41): throttler: Power Manager for reason: Display power management activated
[manager_maybe_start_job_for_window] gs-manager.c:207 (10:59:13): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (10:59:13): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (10:59:42): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (10:59:42): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (11:04:05): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (11:04:05): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (11:07:50): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (11:07:50): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (11:11:25): Not starting job because throttled
[manager_maybe_start_job_for_window] gs-manager.c:207 (11:11:25): Not starting job because throttled
andre at huge:~/gnome-screensaver$
Please tell me if you need more information. This is on Edgy, upgraded
from Dapper. I don't recall seeing this on Dapper.
** Affects: gnome-screensaver (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Throttle status not cleared
https://launchpad.net/bugs/72028
More information about the desktop-bugs
mailing list