Bug 908070

Summary: Laptop brightness settings are not saved permanently
Product: [Fedora] Fedora Reporter: prahladyeri14
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bnocera, collura, kem, mkasik, prahladyeri14, rstrode, tiagomatos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-15 06:09:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description prahladyeri14 2013-02-05 19:11:46 UTC 
Description of problem: I've recently installed Fedora 18 on my Tosiba Satellite C650 Laptop. Everything is working fine until now, except this small glitch. Everytime the machine starts it goes to full brightness mode. Any changes I make through either through the gnome-control-center or by pressing the function keys (F6/F7 keys) are only temporary. The next time my machine starts, brightness is again set to max.


Version-Release number of selected component (if applicable): NA


How reproducible: Positive.


Steps to Reproduce:
1. Start the machine.

2. Open gnome-control-center by going to Activities -> Show Applications -> System Tools -> System Settings

3.Change the brightness setting and restart
  
Actual results:
The brightness settings changed in step-3 should be reflected.

Expected results:
The brightness settings changed in step-3 does not reflect.


Additional info: I've attached the lspci output if it helps.
Comment 1 prahladyeri14 2013-02-05 19:15:58 UTC 
*** Bug 908066 has been marked as a duplicate of this bug. ***
Comment 2 collura 2013-10-12 09:07:54 UTC 
it was suggested that systemd >= 207 fixes the forgetfullness, see:

  https://bugzilla.redhat.com/show_bug.cgi?id=696621#c19
Comment 3 Bastien Nocera 2013-10-15 06:09:42 UTC 

*** This bug has been marked as a duplicate of bug 696621 ***