Bug 799653 - 0% Brightness when wake from sleep when charging
0% Brightness when wake from sleep when charging
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
16
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-03 17:13 EST by timko.charles
Modified: 2012-03-22 15:25 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-03-22 15:25:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description timko.charles 2012-03-03 17:13:38 EST
Description of problem:
Waking from sleep while charging my laptop, the screen brightness is 0%.  You have to login before adjusting the brightness.

Version-Release number of selected component (if applicable):
uname -r ==> 3.1.0-7.fc16.x86_64

How reproducible:
Happens constantly.

Steps to Reproduce:
1. Plug in power chord
2. Let laptop sleep
3. Wake
  
Actual results:
Screen is black

Expected results:
Screen should have the same brightness prior to sleeping

Additional info:
Comment 1 Dave Jones 2012-03-22 13:00:20 EDT
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 2 Dave Jones 2012-03-22 13:04:13 EDT
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 3 Dave Jones 2012-03-22 13:14:59 EDT
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 4 timko.charles 2012-03-22 15:11:18 EDT
Currently running 3.2.10-3.fc16.x86_64, and this problem looks fixed. Will reopen if I am mistaken....

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