Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 185109 - gnome-power-manager tries to suspend the system ever 30 minutes
Summary: gnome-power-manager tries to suspend the system ever 30 minutes
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: rawhide
Hardware: powerpc
OS: Linux
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact:
Depends On:
Blocks: FC5Target
TreeView+ depends on / blocked
Reported: 2006-03-10 18:21 UTC by Jesse Keating
Modified: 2013-03-13 04:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-06-22 19:29:03 UTC

Attachments (Terms of Use)

Description Jesse Keating 2006-03-10 18:21:20 UTC
On a fresh install of 3/09/2006's rawhide on PPC the system will try to suspend
every 30 minutes due to system inactivity.  This seems to be reading the setting
from when to blank the display, not suspend the system.  I'm running a test to
see if it happens on !ppc, won't know for another 20 minutes or so.

Comment 1 Ray Strode [halfline] 2006-03-10 19:26:10 UTC
Can post the output of

gconftool-2 -R /apps/gnome-power-manager

and any relevent log messages to this report?

Comment 2 Jesse Keating 2006-03-10 20:00:14 UTC
gconftool-2 outputs nothing.

Log entry is:

gnome-power-manager: Suspending computer because the system state is idle

Comment 3 Jesse Keating 2006-03-10 20:29:17 UTC
n/m, I forgot -R

 use_icon_for_desktops = false
 check_type_cpu = true
 can_hibernate = true
 ac_sleep_display = 1800
 battery_brightness = 50
 action_button_power = interactive
 lock_on_hibernate = true
 battery_sleep_computer = 1200
 action_ac_button_lid = blank
 lock_on_suspend = true
 dim_on_idle = true
 lock_on_blank_screen = true
 notify_hal_error = true
 ac_brightness = 100
 use_time_for_policy = true
 notify_fully_charged = true
 display_icon_policy = always
 action_button_suspend = suspend
 action_sleep_type = suspend
 notify_ac_adapter = true
 ac_sleep_computer = 0
 battery_sleep_display = 300
 action_battery_button_lid = suspend
 can_suspend = true
 action_button_hibernate = hibernate
 action_battery_critical = shutdown
 check_type_net = true
 lock_use_screensaver_settings = true

Comment 4 Richard Hughes 2006-03-11 13:57:46 UTC
I'm not sure that it is reading the wrong value -- is your inactivity value in
gnome-screensaver-preferences set to 10 minutes by any chance?

The inactivity slider in g-p-m waits for the inactive signal from g-s (default
10 minutes I think) and then starts it's internal countdown (in your case 20
minutes) -- so you get 30 minutes total. g-s decides that the session is idle,
g-p-m decides that the "computer" is idle.

Maybe we should add that to the yelp help, or maybe just start the sliders at
the value set by gnome-screensaver.

Comment 5 Jesse Keating 2006-03-11 14:05:30 UTC
Why would g-p-m be trying to suspend it though?  The preferences for g-p-m state
that it should never sleep.

Comment 6 Richard Hughes 2006-03-11 14:13:14 UTC
Hmm... good question. Is your g-s idle setting set to 30 minutes? We might be
taking the value of 0 to mean "no time", rather than "never".

Comment 7 Jesse Keating 2006-03-11 14:21:23 UTC
I'll have to look at the gnome-screensaver slider.  It is what we do by default
on Fedora, which is probably 10 minutes.  gnome-power-manager setting for
putting the display to sleep is 30, and the system to sleep is Never.  Of note,
this only seems to happen on ppc, a g4 mini mac.

Comment 8 Richard Hughes 2006-03-11 14:24:34 UTC
>Of note, this only seems to happen on ppc, a g4 mini mac.

Odd.. we treat the dpms stuff exactly the same. Are you sure something else
might not be triggering the dpms, say something like an xsetting or the monitor

Comment 9 Jesse Keating 2006-03-11 14:27:22 UTC
Theoretically it could be the LCD, I can disconnect the LCD all together and see
if it still triggers.  I don't think it is any xsetting, I certianly haven't set

Comment 10 Jesse Keating 2006-06-22 19:29:03 UTC
Can't duplicate this anymore.

Note You need to log in before you can comment on or make changes to this bug.