Bug 908799

Summary: Changing screen brightness settings does not work after suspend
Product: [Fedora] Fedora Reporter: Taylor Smock <smocktaylor>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jforbes, jonathan, kedaly7, kernel-maint, madhu.chinakonda
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-10 14:41:10 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:
Attachments:
Description Flags
dmesg after suspend none

Description Taylor Smock 2013-02-07 14:54:51 UTC
Created attachment 694542 [details]
dmesg after suspend

Description of problem:
Before suspending, the computer can use the Fn+[brightness] keys to change the brightness. The brightness slider is also available in the Gnome Power Settings panel.
After suspend, the brightness keys do not work and the brightness slider is unavailable.
su -c "echo '[number]' >> /sys/class/backlight/intel_backlight/brightness"
does work.

Version-Release number of selected component (if applicable):
All tested Fedora releases (also affects other distributions).

How reproducible:
Always


Steps to Reproduce:
1. Start up normally
2. Suspend
3. Start up from suspend
4. Attempt to change brightness settings normally
  
Actual results:
Brightness does not change.

Expected results:
Brightness should change.


Additional info:
Attempted under Rawhide, F18, F17, and Ubuntu 12.10.
The display keeps the brightness that was set prior to suspend.
May be a duplicate of Bug 808942. (Filed as a separate bug since I cannot tell whether or not it is the same bug affecting this laptop).
Laptop: Fujitsu T731
Video: Intel HD 3000

Line 1324/1348 in the dmesg output (attached) states that it is restoring the backlight state.

Comment 1 Kevin Daly 2013-03-16 21:34:01 UTC
I am also having this problem.. I've found a workaround that fixes this, it's documented here. 

http://lists.fedoraproject.org/pipermail/power-management/2013-March/000092.html

There are patches as well from Canonical that fix this problem..

Might be worth looking at this.

https://launchpad.net/~canonical-hwe-team/+archive/sputnik-kernel

Patch #954661 and #1055231 might give insight to you guys on fixing this.

Comment 2 Fedora End Of Life 2013-04-03 15:43:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 3 Justin M. Forbes 2013-04-05 18:48:24 UTC
Is this still an issue with the 3.9 kernels in F19?

Comment 4 Taylor Smock 2013-04-11 11:19:16 UTC
It is still an issue with the 3.9 kernels.

Comment 5 Josh Boyer 2013-09-18 20:34:38 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 6 Taylor Smock 2013-09-26 10:58:55 UTC
It is still present in 3.11.1-300.fc20.x86_64 (I'm running F20 alpha), so it should still be present in 3.11.1-200.fc19.

Comment 7 Justin M. Forbes 2014-01-03 22:09:19 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 8 Justin M. Forbes 2014-03-10 14:41:10 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.