GNOME Bugzilla – Bug 660395
bad default setting: suspend after 30min when plugged in
Last modified: 2011-10-05 18:10:03 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/860485 "By default power setting is set to 'suspend after 30 min when plugged in' it should be 'Don't suspend'" according to our packagers: "The system won't suspend, since the daemon uses the sleep-inactive-ac (and -battery) GSettings keys, but it's a bug in the UI, which is now fixed in GIT (both master and 3-2 branch) and is coming in the next g-c-c upload" The fix is applied but the systems are still having the problem, debugging log is at : https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/860485/+attachment/2476531/+files/debug.txt
Feel free to talk to Martin about that one. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 624330 ***
<key name="sleep-inactive-ac" type="b"> <default>false</default> <summary>Enable the inactive computer sleep when on AC power</summary> <description>Whether to put the computer to sleep when inactive on AC power.</description> </key> <snip> <key name="sleep-inactive-battery" type="b"> <default>false</default> <summary>Enable the inactive computer sleep when on battery power</summary> <description>Whether to put the computer to sleep when inactive on battery power.</description> </key> We're not support to suspend by default. But it turns out that the config options aren't even read.
(In reply to comment #2) > We're not support to suspend by default. Supposed to even.
In master only: commit b667ef06b1950b088ffee6f7f7722e2e05eb5a22 Author: Richard Hughes <richard@hughsie.com> Date: Thu Sep 29 14:42:35 2011 +0100 power: Remove some unused schema for enabling the sleep-inactive actions This was originally added in gnome-3-2 as the designers specified having a checkbox next to the sleep timeout to control whether the action was enabled or disabled, and we didn't want to reset the action to the default every time the user clicked and unclicked the enable button. It turns out the designers changed thier mind on the design, and so it was changed late in the GNOME 3.2 cycle. These obsolete config options remained. Resolves half of https://bugzilla.gnome.org/show_bug.cgi?id=660395
And the other half, and also in in gnome-3-2: commit 378e3037ac09b8851ad83261930295f3eceb590c Author: Richard Hughes <richard@hughsie.com> Date: Thu Sep 29 15:04:22 2011 +0100 power: Do not sleep-on-idle by default We do not actually read the boolean keys in gnome-settings-daemon due to a mixup when the UI was re-designed. We can just change the default of the timeout key (that we do read...) to zero to change "never" to be the default. Note: we're not actually going to remove the unused keys from the schema like we did in master, otherwise upgrading the g-s-d package whilst the control center is open is going to make it explode. Resolves https://bugzilla.gnome.org/show_bug.cgi?id=660395 Can somebody please test gnome-settings-daemon and gnome-control-center from gnome-3-2 branches and confirm that it fixes it for them too. Thanks.
It occurred to me that this is the reason my F16alpha (and now my F16beta) libvirt guests have, within the last few days, started to wedge after 30 minutes. And no amount of vnc keyboard or mouse activity is going to wake it up. Hopefully this fix will cure libvirt guests as well. I'll wait and see when 3.2.1 hits the F16 updates-testing repo. And if not, well, then you heard it here first.