Bug 908070 - Laptop brightness settings are not saved permanently
Summary: Laptop brightness settings are not saved permanently
Keywords:
Status: CLOSED DUPLICATE of bug 696621
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 908066 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 19:11 UTC by prahladyeri14
Modified: 2013-10-15 06:09 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-15 06:09:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


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