GNOME Bugzilla – Bug 694525
power management settings
Last modified: 2013-04-13 14:16:52 UTC
The code handling screen dimming and power saving in general has been extensively reworked in 3.8, and the particular keys that are mentioned here don't actually exist anymore. I believe that you can now control the dimming by using org.gnome.desktop.session.idle-delay and org.gnome.settings-daemon.plugins.power.idle-dim. Bastien, can you provide details for how this page needs to be updated: http://help.gnome.org/admin/system-admin-guide/stable/power-settings.html.en
org.gnome.settings-daemon.plugins.power idle-brightness will change the level of brightness to use when the machine isn't used for a little while. org.gnome.settings-daemon.plugins.power idle-dim will change whether or not to drop the level of brightness when unused. org.gnome.desktop.session idle-delay will change when the screensaver comes on and the display will be blanked.
Created attachment 239669 [details] [review] Modified the gsettings keys Hi, I've added the gsettings keys mentioned by Bastien and also included small descriptions for each based on Bastien's comment. Hope it's okay! Thanks!
Review of attachment 239669 [details] [review]: ::: system-admin-guide/C/power-settings.page @@ +26,1 @@ <p>System-wide power management settings are controlled by gsettings keys. These settings are not system-wide - the settings of the active session are used (and applied by the settings-daemon that is running inside that session). @@ +27,3 @@ For instance, <em>dim screens after X minutes</em> is controlled by the</p> + <p><file>org.gnome.settings-daemon.plugins.power.idle-brightness</file>, which + controls the level of brightness to be used when the machine is idle for a I would say 'brightness level' instead of 'level of brightness' @@ +33,2 @@ <p>and</p> + <p><file>org.gnome.settings-daemon.plugins.power.idle-delay</file>, which decides org.gnome.desktop.session.idle-delay
Created attachment 241151 [details] [review] Changes after review Thank you so much for the review Matthias. :) I have made the changes suggested. Thank you. :)
Review of attachment 241151 [details] [review]: You are listing a number of items, use a list for this. A definition list may be appropriate as you are explaining what each key does. The keys are not files, they would be better marked up as <code> or <cmd>, check how they are marked up on other pages, for example using "git grep -n 'org.gnome.' system-admin-guide/C/". If these are marked up inconsistently, pick the style that seems most logical to you and update the markup for the other instances after you finish with this bug.
Usage "a little while" could be improvised to "some time", I think. When you are using a definition list to explain the keys, you would need to reword your descriptions appropriately that is to say starting a description with "which controls whether or not to drop" would be not be good sentence construction.
Created attachment 241283 [details] [review] Updated Mallard tags. Changes according to Kat's review. Sindhu, is the language okay? :)
Review of attachment 241283 [details] [review]: ::: system-admin-guide/C/power-settings.page @@ +35,3 @@ + <item> + <title><cmd>org.gnome.settings-daemon.plugins.power.idle-dim</cmd></title> + <p> Decides whether the brightness level must be dropped when the Remove the space between <p> and Decides before you push! "Set" sounds better than "decides". @@ +40,3 @@ + <item> + <title><cmd>org.gnome.desktop.session.idle-delay</cmd></title> + <p>Decides the idle time after which the screen must be blanked and the Same here.
Review of attachment 241283 [details] [review]: ::: system-admin-guide/C/power-settings.page @@ +35,3 @@ + <item> + <title><cmd>org.gnome.settings-daemon.plugins.power.idle-dim</cmd></title> + <p> Decides whether the brightness level must be dropped when the "Set" sounds better than "decides" because the gsettings key is an inanimate object and cannot "decide" like a human :) Please see to it that in future you do not add human-like qualities to inanimate objects, one such common mistake is using "'s" for programs. Example: Gedit's.
Created attachment 241322 [details] [review] Minor update Kat, there's a really small change: "Sets the drop in the brightness level when the machine is idle" instead of "Decides whether or not to drop the brightness level when the machine is idle". If that's okay, I can push to master.
Sindhu, does it read okay now? :)
Review of attachment 241322 [details] [review]: ::: system-admin-guide/C/power-settings.page @@ +27,3 @@ + instance, <em>dim screens after X minutes</em> is controlled by the + following gsettings keys:</p> + <terms> The second sentence seems to merge two ideas together. An example and the introduction to the list. Maybe it can be improvised? Quoting from GDP Style Guide (https://developer.gnome.org/gdp-style-guide/2.32/gdp-style-guide.html) Topic 7 How to introduce lists and procedures Rule See Section 2.5 ― Lists. Example In the Properties dialog select: Rewrite In the Properties dialog select the following parameters: Exceptions Single nouns in front of a colon are acceptable, as opposed to a sentence fragment. For example, if the preceding paragraph discusses parameters, you can introduce the list of parameters in the following way: Parameters: [Snipped for brevity] Perhaps you can add a <title> after <terms> tag to say "Gsettings keys:" ?
Created attachment 241325 [details] [review] Minor update 2 I thought that was ok because there's only one kind of parameter: Gsettings keys. Does this read better?(I first had just "controlled by:" and then thought "controlled by the following" was better)
Review of attachment 241322 [details] [review]: Pushed to master: https://git.gnome.org/browse/gnome-user-docs/commit/?id=4c3c33a4e993c1c5e56e4a77a264d47c87430f87