Bug 693639 - gnome-power-manager resets custom brightness level
gnome-power-manager resets custom brightness level
Status: CLOSED WORKSFORME
Product: Fedora
Classification: Fedora
Component: gnome-power-manager (Show other bugs)
14
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Richard Hughes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-05 03:46 EDT by Christoph Wickert
Modified: 2011-11-15 08:39 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-11-15 08:39:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Christoph Wickert 2011-04-05 03:46:44 EDT
Description of problem:
When on battery, gnome-power-manager resets custom brightness levels.

Version-Release number of selected component (if applicable):
gnome-power-manager-2.32.0-3.fc14.x86_64 and any later version

How reproducible:
always

Steps to Reproduce:
1. Configure g-p-m to "Reduce backlight brightness" on battery
2. Go on battery and set a custom brightness level with the function keys. This is a very common use case, e.g. you are travelling
3. wait a little until the timeout for "Dim brightness when idle" has been reached. Note: This option is turned *OFF*
  
Actual results:
Brightness gets dimmed to default level again.

Expected results:
Brightness should not change for this session where "session" means
- until the laptop has been suspended OR
- until the display has been locked OR
- until "Put laptop to sleep when  inactive for" or any other timeout from g-p-m has been reached,  but NOT the timeout for "Dim brightness when idle" especially when this option is not enabled.

Additional info:
Comment 1 Richard Hughes 2011-11-15 08:39:38 EST
This should be fixed in F16, please reopen if that's not the case. Thanks.

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