Bug 990844 - Power Settings are not persistent
Power Settings are not persistent
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: control-center (Show other bugs)
19
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Control Center Maintainer
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-01 01:58 EDT by Onyeibo Oku
Modified: 2013-11-06 08:17 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-06 08:17:33 EST
Type: Bug
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 Onyeibo Oku 2013-08-01 01:58:28 EDT
Description of problem:
By default Fedora boots up with 100% display brightness and Suspend set.  I find that while in some machines disabling Suspend may fail ... setting brighness is guarranteed works only during the session.  Rebooting resets the brightness back to 100%.  This is exhausting. 

Version-Release number of selected component (if applicable):
control-center.x86_64            1:3.8.3-2.fc19

How reproducible:
consistent ... tested on two machines

Steps to Reproduce:
1. Boot Fedora-19
2. Change Power settings: lower brightness to 0%, turn off Automatic Suspend
3. Reboot

Actual results:
Settings revert back and is apparent on boot.  Screen glare is at 100% and machine *may* suspend (I think the suspend one is machine dependent.  The settings will show currectly but machine still suspends anyways)

Expected results:
Settings should remain.  Brightness should be 0% at boot and suspend should obey the settings

Additional info:
Both Machines were Dell laptops (Vostro 1514 and Inspiron 1764
Comment 1 Onyeibo Oku 2013-11-06 08:17:33 EST
Migrated to Fedora-20 (pre-release).  Bug appears to have been fixed

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