Bug 700994 - "Dim screen to save power" has no effect
Summary: "Dim screen to save power" has no effect
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-30 10:18 UTC by Philipp Dörfler
Modified: 2012-03-05 17:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-11-15 13:36:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Philipp Dörfler 2011-04-30 10:18:02 UTC
Description of problem:
Setting "Dim screen to save power" in gnome-power-manager has no effect

Version-Release number of selected component (if applicable):
gnome-power-manager-3.0.0-1.fc15.x86_64

How reproducible:
Always reproducible.

Steps to Reproduce:
- Open gnome's system settings in gnome3
- click on "screen"
- check "Dim screen to save power"
- unplug the power cord so the laptop runs on battery
  
Actual results:
The screen's brightness remains unchanged.

Expected results:
The screen should dim to save power.

Additional info:
Opening dconf-editor and manually toggling org.gnome.power-manager.backlight-battery-reduce works as expected. It seems that gnome-power-manager should toggle this setting in dconf, but doesn't.

Comment 1 Richard Hughes 2011-11-15 13:36:42 UTC
This should be fixed in F16, please reopen if that's not the case. Thanks.

Comment 2 Gordon Messmer 2012-03-05 17:10:42 UTC
Since this is one of the top google hits for "gnome dim screen to save power", I wanted to update this entry.

The "Dim screen to save power" option currently sets the dconf value /org/gnome/settings-daemon/plugins/power/idle-dim-battery.  As far as I can tell, there is no setting anywhere in GNOME 3 (in Fedora 16) that will dim the screen when a PC switches from external to battery power.


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