Bug 1001440

Summary:	Screen brightness doesn't increase or decrease accurately
Product:	[Fedora] Fedora	Reporter:	Grahams Nguimbi <ganguimbi>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	19	CC:	collura, dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa
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-08 16: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 Grahams Nguimbi 2013-08-27 04:46:35 UTC

Description of problem:
Every time I press on my HIGH (+) and LOW (-) SCREEN BRIGHTNESS button on my laptop, the brightness doesn't increase or decrease accurately. It changes from extremely high to extremely low brightness.

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


How reproducible:
Simply click on the HIGH or LOW SCREEN BRIGHTNESS to see how the brightness change inaccurately.


Actual results:
Screen brightness changes from high to low brightness.

Expected results:
I expect to change accurately the screen brightness (For example, I want to be able to set my brightness to 22% or 54% or 87% brightness. Right now, I can only set my brightness from 0% to 100% brightness)

Additional info:

Fedora 19

Comment 1 Josh Boyer 2013-09-18 20:28:20 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:09:42 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.