Bug 956746 - Backlight minimum on resume (only when using Suspend from system menu)
Summary: Backlight minimum on resume (only when using Suspend from system menu)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-25 14:20 UTC by Michal Domonkos
Modified: 2015-02-17 15:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:04:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output (209.12 KB, text/plain)
2013-04-25 14:38 UTC, Michal Domonkos
no flags Details

Description Michal Domonkos 2013-04-25 14:20:46 UTC
Description of problem:
After sleep/resume cycle the laptop screen is set to the lowest brightness level available. This happens only if sleeping the machine from the system menu in the top right corner. It is then possible to increase brightness normally via the hardware keys.

When suspending by closing the lid or pressing the hardware button, the brightness restores normally on resume.

Laptop: ThinkPad T520
Graphics:
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

Version-Release number of selected component (if applicable):
kernel-3.9.0-0.rc8.git0.2.fc19.x86_64
xorg-x11-drv-intel-2.21.6-1.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. Go to the system menu by clicking your username in the top right corner
2. Press down Alt key
3. Click Suspend
4. After the machine has been suspended, resume by pressing the power button
  
Actual results:
Brightness level set to minimum, has to be increased manually

Expected results:
Brightness level should be restored correctly

Comment 1 Michal Domonkos 2013-04-25 14:38:53 UTC
Created attachment 739935 [details]
dmesg output

Comment 2 Fedora End Of Life 2015-01-09 17:58:23 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 15:04:21 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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