Bug 795681 - Laptop screen doesn't come back on after resume
Laptop screen doesn't come back on after resume
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-02-21 04:44 EST by Reinout van Schouwen
Modified: 2013-02-13 03:14 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 03:13:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Reinout van Schouwen 2012-02-21 04:44:55 EST
Description of problem:

Since about 1-2 months or so, my laptop (Dell Latitude E6410, intel graphics) screen doesn't come back after I resume from suspend. I can see the backlight but the screen stays black. Ctrl+Alt+Backspace or Ctrl+Alt+F2 for console doesn't make a difference.

This is a regression, the initial Fedora 16 release didn't have this problem. I would have to press the Fn+Auto brightness key to re-enable the backlight sometimes, but that was all. Therefore I suspect an update to be the culprit.

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

How reproducible:

Steps to Reproduce:
1. Go to the user menu, click Suspend
2. After suspend, press the power key to wake the system
Actual results:
Laptop wakes up, screen stays black

Expected results:
Laptop wakes up, lock screen shows up

Additional info:
My smolt profile is here: http://www.smolts.org/client/show/pub_b3dcc293-7ba7-4688-80ec-abc89641e09d
Comment 1 Josh Boyer 2012-02-21 09:51:12 EST
I think Keith had some patches to fix an issue similar to this but I don't recall if they got applied upstream or in -stable.
Comment 2 Szőke Károly 2012-05-16 15:56:12 EDT
The last good kernel was 3.1.9, after that, from 3.2.x it is bad.
Comment 3 Fedora End Of Life 2013-01-16 05:02:16 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
Comment 4 Fedora End Of Life 2013-02-13 03:14:34 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.