Bug 626612 - After being blanked by gnome-power-manager, display never wakes up again
Summary: After being blanked by gnome-power-manager, display never wakes up again
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau (Show other bugs)
(Show other bugs)
Version: 14
Hardware: All Linux
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-23 23:17 UTC by Adam Williamson
Modified: 2012-08-16 17:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-16 17:38:21 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dmesg output after triggering the blank then re-opening the lid (122.75 KB, text/plain)
2010-08-23 23:18 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2010-08-23 23:17:54 UTC
On the affected system, I have gnome-power-manager set to blank the display if the lid is closed with AC power connected. If I trigger this blank, then open the lid again and use the trackpad or touch a key - which should wake the screen up again - it stays blank. The system is still running (I could pull dmesg via an ssh link), but the screen won't come back until I reboot. dmesg with drm.debug=14 set attached, as requested.

Comment 1 Adam Williamson 2010-08-23 23:18:32 UTC
Created attachment 440520 [details]
dmesg output after triggering the blank then re-opening the lid

Comment 2 Martin Thurn 2011-12-23 19:09:15 UTC
This still happens on Fedora 15.  On a desktop computer (HP Evo d530), when the "time limit" is reached and the screen goes blank, wiggling the wired USB mouse and pressing every key on the wired USB keyboard does nothing.  Have to cold boot by holding the power button for 5 seconds, losing all my work.  This makes Fedora pretty much useless.  Severity should be increased.

Comment 3 Adam Williamson 2012-01-03 23:28:57 UTC
not likely to be the same bug, I don't think. I haven't had this issue on F15 or F16.

Fedora Bugzappers volunteer triage team

Comment 4 Fedora End Of Life 2012-08-16 17:38:24 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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: 

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