GNOME Bugzilla – Bug 624330
Have default settings be more energy star 5.0 compliant
Last modified: 2011-09-29 09:44:31 UTC
Energy star is a standard backed by the US government to set standards for energy use of devices. The specification for Operating System settings can be found here: http://www.energystar.gov/index.cfm?c=revisions.computer_spec Spec direct link (page 13): http://www.energystar.gov/ia/partners/prod_development/revisions/downloads/computer/Version5.0_Computer_Spec.pdf Also to better help understand Energy Star. The Open Suse team actually heavily looked into this, and have a great presentation here: http://files.opensuse.org/opensuse/en/3/34/EnergyStar.pdf The reason you want to be Energy star compliant: - Many retailers will not sell machines that are not Energy Star compliant - Most Government agencies will not buy hardware solutions that are not Energy Star compliant - OEMs are now pushing heavily to have all hardware be Energy Star compliant - The OS software default settings are apart of the Energy Star compliance of machines There are only two default settings preventing the stock gnome-power-manager from being energy star compliant: * DPMS-off the display within 15 minutes of user inactivity when on A/C - Currently this is set to 30 min. So setting it to 15 or below would fix this. * Activate computer's Sleep mode within 30 minutes of user inactivity when on A/C. - Currently this is set to never - It is also understood that this could potentially have user experience impact - It might not work on some desktop boxes For the latter point, I think a reasonable compromise would be to default to suspend after 30 minutes of inactivity only when we are on battery. In that case we have a laptop, where suspend/resume is fairly reliabe these days. Do you think these changes are appropriate for upstream?
Created attachment 165883 [details] [review] proof of concept patch for 2.30 Since a patch says more than a thousand words, this is what I have in mind. This patch is against 2.30. If you like the idea, I'm happy to provide one for git head (in particular, gconf->gsettings).
Please reassign to gnome-settings-daemon as this functionality is controlled from there now.
Comment on attachment 165883 [details] [review] proof of concept patch for 2.30 the original patch is not relevant any more, as the default timeouts in the g-s-d plugin are now Energy Star compliant.
So again, the only default which isn't Energy Star compliant is org.gnome.settings-daemon.plugins.power sleep-inactive-battery, which is off by default right now.
We don't actually want to enable automatic suspend by default, because, as opposed to clicking on the "Suspend" button, closing the lid, or pressing the power button, we have a potentially destructive reaction that's not in response to a user action, but to user inaction. (Was discussed with Richard, based on discussions with mjg59 as well).
*** Bug 660395 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > We don't actually want to enable automatic suspend by default, because, as > opposed to clicking on the "Suspend" button, closing the lid, or pressing the > power button, we have a potentially destructive reaction that's not in response > to a user action, but to user inaction. I totally agree. However, it seems that GNOME 3.2 now actually does enable suspend after 30 minutes of inactivity by default, even when being on AC. This already caused some trouble here when I was rsyncing a DVD over lunch break. That's why I originally proposed to set the 30 minutes only when on battery, as it's more justifyable there.
<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 used.