GNOME Bugzilla – Bug 500482
Power Manager shows an 'Inhibit Warning' which is misleading
Last modified: 2009-03-04 14:48:10 UTC
Please describe the problem: Banshee SVN stable (0.13.2) tries to inhibit gnome power manager but the laptop still goes into standby despite the warning of overheating. Steps to reproduce: 1. Run Banshee SVN stable (0.13.2) 2. Play a music track, the inhibit warning appears. 3. Close the lid (pm settings are to go into standby when the lid is closed) 4. The laptop *does* go into standby despite the inhibit warning invoked by Banshee. Actual results: The laptop goes to sleep. WHen opening the lid, banshee resumes playing the track from where it was prior to standby. Expected results: Following the warning, I'd expect the laptop to remain awake even when the lid is closed. Does this happen every time? Yes. Other information: This might be useful: http://bugzilla.gnome.org/show_bug.cgi?id=344946 Here's some output: [gpm_cell_array_update] gpm-cell-array.c:277 (10:51:29): no devices of type 4 [gpm_prefs_server_set_capability] gpm-prefs-server.c:84 (10:51:29): capability now 13 [gpm_engine_get_icon] gpm-engine.c:391 (10:51:29): Trying CRITICAL icon: primary, ups, mouse, keyboard *** WARNING *** [gpm_warnings_get_state_percentage] gpm-warnings.c:104 (10:51:29): percentage zero, something's gone wrong *** WARNING *** [gpm_warnings_get_state_percentage] gpm-warnings.c:104 (10:51:29): percentage zero, something's gone wrong *** WARNING *** [gpm_warnings_get_state_percentage] gpm-warnings.c:104 (10:51:29): percentage zero, something's gone wrong [gpm_engine_get_icon] gpm-engine.c:423 (10:51:29): Trying CHARGING icon: primary, ups [gpm_engine_get_icon] gpm-engine.c:435 (10:51:29): no devices (dis)charging, so no icon will be displayed. [gpm_profile_get_accuracy] gpm-profile.c:847 (10:51:29): corrected percentage... [gpm_cell_array_get_description] gpm-cell-array.c:960 (10:51:29): accuracy = 100 [gpm_profile_get_time] gpm-profile.c:310 (10:51:29): percentage = 100, correcting to 99 [gpm_engine_get_summary] gpm-engine.c:349 (10:51:29): tooltip: Computer is running on AC power Laptop battery fully charged (100%) Provides 2 hours 40 minutes battery runtime [gpm_engine_recalculate_state_summary] gpm-engine.c:603 (10:51:29): ** EMIT: summary-changed(1): Computer is running on AC power Laptop battery fully charged (100%) Provides 2 hours 40 minutes battery runtime [gconf_key_changed_cb] gpm-conf.c:332 (10:51:29): emitting value-changed : '/apps/gnome-screensaver/power_management_delay' [gconf_key_changed_cb] gpm-screensaver.c:181 (10:51:29): key : /apps/gnome-screensaver/power_management_delay [gpm_inhibit_inhibit] gpm-inhibit.c:191 (10:51:36): Recieved Inhibit from 'Banshee' (:1.30) because 'Playing Music' saving as #2095846334 *** WARNING *** [gpm_notify_create] gpm-notify.c:124 (10:51:36): libnotify: Power Manager : Your laptop will not sleep if you shut the lid as it is currently inhibited. Some laptops can overheat if they do not sleep when the lid is closed. [gpm_inhibit_un_inhibit] gpm-inhibit.c:234 (10:51:39): UnInhibit okay #2095846334 [gpm_inhibit_inhibit] gpm-inhibit.c:191 (10:51:39): Recieved Inhibit from 'Banshee' (:1.30) because 'Playing Music' saving as #80703508 *** WARNING *** [gpm_notify_create] gpm-notify.c:124 (10:51:39): libnotify: Power Manager : Your laptop will not sleep if you shut the lid as it is currently inhibited. Some laptops can overheat if they do not sleep when the lid is closed. [notify_closed_cb] gpm-notify.c:89 (10:51:43): caught notification closed signal [notify_closed_cb] gpm-notify.c:89 (10:51:44): caught notification closed signal
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.