Bug 1107872

Summary: Laptop does not wake up from sleep, no matter what!
Product: [Fedora] Fedora Reporter: Dhaval Anjaria <dhv2712>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 20CC: airlied, ajax, bskeggs, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Consequence: Fix: ok, so i found this "temporarly fix". When you are using laptop, first lock your screen and then close lid to sleep mode. After you open lid system will work ok, but notifications area will show: "Power Manager not authorized". I'm also have raden card (IBM t43). Result:
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-10 15:02:16 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
The output of journalctl -f while I try to solve this issue while ssh'd into the machine. none

Description Dhaval Anjaria 2014-06-10 21:19:09 UTC 
Created attachment 907427 [details]
The output of journalctl -f while I try to solve this issue while ssh'd into the machine.

Description of problem:
When the laptop goes to sleep, I get a blank screen, from which I cannot recover. No matter what I do, the keyboard does not respond, nothing happens and I have to reboot the laptop to be usable again

This is a bug that affects everything from nouveau to nvidia to ati drivers.

How reproducible:
Set laptop to sleep, either through the keyboard (usually Fn + F1), or set it to sleep in the Power Management settings in your DE of choice.

Steps to Reproduce:
1. Set laptop to Sleep

Actual results:
Laptop screen stays blank with the keyboard being unresponsive (i.e. CapsLock not turning on when pressed)

Expected results:
Laptop wakes up from sleep, and the keyboard is responsive

Additional info:
I can ssh into the machine and use it while it is in this state. I can also start a VNC server and use a desktop with it. I tried, through the systemctl command, restarting graphical.desktop and gdm.service. I tried `sudo pkill X`, I tried going to multi-user.target but none of this works.

Attached with this Bug is a journalctl output of what happens when the laptop goes to sleep and while I try to recover it.


I'm using kernel-3.14.3-200.fc20.x86_64, on Fedora 20 with KDE, GNOME 3 and a few other desktops installed. This, surprisingly, does not happen on GNOME 3 because GNOME3 does not have an option for Sleep, only Suspend while KDE does not have an option for Suspend, only Sleep. pm-suspend has the same effect as stated above. On MATE and KDE, when I resume from Sleep, this problem persists, but not GNOME. This has been an issue for a VERY long time apparently, so I really hope this gets resolved or at least the journalctl-logs help. 

journalctl logs pastebin:
http://paste.fedoraproject.org/108794/35116140
Comment 1 Ben Skeggs 2014-06-10 22:58:13 UTC 
Not sure why you assigned this to Nouveau, given the comment that it doesn't matter what video driver you're using.. Reassigning to kernel.
Comment 2 Dhaval Anjaria 2014-08-09 10:43:14 UTC 
So I have a little workaround, but it's not really a workaround. In KDE power management I simply set it to either Turn off the screen or Lock Screen. I don't have it set to sleep in any event.
Comment 3 Justin M. Forbes 2014-11-13 16:03:10 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  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 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.
Comment 4 Justin M. Forbes 2014-12-10 15:02:16 UTC 
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 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.