Bug 326685 - Resuming from hibernate shows blank screen yet usable login screen
Summary: Resuming from hibernate shows blank screen yet usable login screen
Status: RESOLVED UNMAINTAINED
Alias: None
Product: lightdm
Classification: Plasma
Component: greeter (other bugs)
Version First Reported In: master
Platform: Kubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-26 14:02 UTC by Mario Ray Mahardhika
Modified: 2020-10-10 21:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Ray Mahardhika 2013-10-26 14:02:49 UTC
After resuming from hibernate, I get a blank screen with only mouse cursor visible. Tried to login with virtual terminal and running `top` I see nothing suspectible. Going back to the GUI subsystem I tried to type password (still with blank screen) and press enter. Voila! The desktop appears.

Reproducible: Always

Steps to Reproduce:
1. Hibernate from a running system
2. Resume

Actual Results:  
On step 2, only mouse cursor is visible, everything else is blank screen

Expected Results:  
On step 2, login dialog appears

by login dialog, I mean a dialog to open the locked screen, because the default settings is to lock screen after suspend/hibernate.
Comment 1 John Andersen 2013-12-13 19:23:29 UTC
Also seen with Opensuse 12.3 and KDE 4.11.4

This only happens if I leave the machine for a long time, (several hours) and it goes into suspend mode by virtue of the settings.   Upon return, screen is black, and system appears suspended to ram.

Pressing power button wakes the system.  However  all I see is the opensuse logo splash screen displayed, but no unlock (password) screen appears, and no mouse or keyboard input will accepted by this session.

Changing to a console, and logging in as root I can see that the session appears to by fully up and running, and the last log message is systemd-sleep(nnn) System Resumed.

Again from the console as root, looking for tasks running under the user logged on at the time of suspend, there is a task called kscreenlocker_g running with a relatively high pid (suggesting it was one of the most recent tasks started by that user).  

killing this task (kscreenlocker_g) and switching back to console 7 showed the system login screen had popped up, and I was able to log back into the session as normal.

Note:
 If I close the lid (instead of just letting it time out) it always works when I re-open the lid, and the log in screen is shown.

This is difficult to test without setting your suspend to ram time to be quite short.
Comment 2 Mario Ray Mahardhika 2014-01-05 00:39:38 UTC
The issue seems to have gone and becomes the old kwin 100% cpu when resuming from hibernate/sleep with desktop effects enabled issue in the latest Kubuntu Saucy update (KDE 4.11.3 Qt 4.8.4 kernel 3.11.0-15-generic 32-bit). Simply turning off desktop effects before hibernate/sleep fixes the issue.
Comment 3 Andrew Crouthamel 2018-11-11 04:36:00 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:27:36 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Nate Graham 2020-10-10 21:20:54 UTC
We no longer use lightDM, having moved to SDDM several years ago. As such, this bug report is no longer applicable. Bugs reports for the new SDDM-based login screen should be filed to one of two places:

1. Visual/UI bugs with the login screen UI itself, or feature requests: plasmashell | Theme - Breeze
2. Bugs with the login/user switching process: https://github.com/sddm/sddm/issues