Bug 1000635

Summary:	Keyboard backlight is not restored when line power is resumed
Product:	[Fedora] Fedora	Reporter:	Bill Gradwohl <bill>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	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:11:24 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:

Description Bill Gradwohl 2013-08-23 22:19:39 UTC

Description of problem:
Asus laptop. When running on battery power, the idle timeout blanks the screen and kills the keyboard backlight. When line power is restored, the keyboard backlight is not resumed.

Version-Release number of selected component (if applicable):
F19 Experienced the same issue on F17.

How reproducible:
Run on battery power and allow the idle timeout to turn down the screen and keyboard backlight. Then resume line power and the backlight does not resume. 

I have to :

echo 1 >/sys/devices/platform/asus_laptop/leds/asus\:\:kbd_backlight/brightness

to get them turned on again.

Comment 1 Josh Boyer 2013-09-18 20:30:31 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:11:24 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.