This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 489133 - Power management preferences
Power management preferences
Product: Fedora
Classification: Fedora
Component: gnome-power-manager (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-03-07 18:23 EST by ametedinov
Modified: 2009-08-20 07:42 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-08-20 07:42:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)

  None (edit)
Description ametedinov 2009-03-07 18:23:55 EST
Make the settings in power management preferences to be changed for the entire system, not just for the user. For example, I want to alway keep my laptop display brightness at the lowest level but when I log off, at the login screen the display brightness is at 100 percent. Example 2: If I create a new account, the display brightness for it will be 100% initially. 

How can I make the display brightness to be at lowest level when I am logged off or in other words at the login screen? How can I make this change for all users without having to go log in to every single account?
Comment 1 ametedinov 2009-03-07 18:35:11 EST
I found it "make default" does this.

Add a description in the box that tells the user what "Make Default" stands for and what it does.
Comment 2 Josh Boyer 2009-03-07 21:42:43 EST
powertop has nothing to do with power management preferences.  Please start filing such bugs against gnome-power-manager
Comment 3 Richard Hughes 2009-08-20 07:42:21 EDT
(In reply to comment #1)
> Add a description in the box that tells the user what "Make Default" stands for
> and what it does.  

Patches welcome. Please file this upstream on the component.

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