Bug 1004098 - Brightness fn shortcuts unresponsive, stuck on 100% [NEEDINFO]
Summary: Brightness fn shortcuts unresponsive, stuck on 100%
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-03 23:13 UTC by Sam Tuke
Modified: 2014-03-10 14:41 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-10 14:41:56 UTC
Type: Bug
jforbes: needinfo?


Attachments (Terms of Use)

Description Sam Tuke 2013-09-03 23:13:39 UTC
Description of problem:

The screen brightness of my Lenovo B570 laptop is no longer responsive to the fn shortcut keys since my upgrade from Fedora 18 to Fedora 19 via FedUp. The shortcut keys have worked since F16 and through all subsequent upgrades until now. When pressed, the shortcuts show the OSD brightness value, but although the % bar changes, the brightness does not, and remains on full at all times.

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

Kernel 3.10.9-200.fc19.i686

How reproducible:

Always

Steps to Reproduce:
1. Install Fedora 18 on a Lenovo B570
2. Upgrade to F19 via FedUp
3. Try changing screen brightness via fn + D-pad up arrow

Actual results:

OSD appears and indicates change, but brightness doesn't change

Expected results:

Brightness changes

Additional info:

Comment 1 Josh Boyer 2013-09-18 20:35:24 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Josh Boyer 2013-10-08 16:07:56 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 3 Sam Tuke 2013-10-08 16:19:17 UTC
This bug is still alive and damaging eyes on kernel 3.11.3-201.fc19.i686.

I've been having to wear sunglasses to dull the brightness:
https://joindiaspora.com/posts/3123769

Comment 4 Sam Tuke 2013-10-28 00:01:02 UTC
This bug is still alive in kernel 3.11.6-200.fc19.i686

This regression was introduced with Fedora 19. Since at least Fedora 16 the problem did not exist.

Comment 5 Justin M. Forbes 2014-01-03 22:09:36 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 6 Josh Boyer 2014-01-08 14:24:49 UTC
Resetting status.  We didn't make any explicit changes so it shouldn't be in MODIFIED.  Please test 3.12.6 as comment #5 suggests, or test 3.13.0-rcX from rawhide or the nodebug repo.

Comment 7 Justin M. Forbes 2014-03-10 14:41:56 UTC
*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.


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