Bug 357315 - Resume from Standby (Suspend to RAM) results in black screen (but with themed cursor)
Summary: Resume from Standby (Suspend to RAM) results in black screen (but with themed...
Status: RESOLVED FIXED
Alias: None
Product: ksmserver
Classification: Plasma
Component: general (show other bugs)
Version: 5.5.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-29 21:25 UTC by Gregor Mi
Modified: 2021-03-20 19:51 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Mi 2015-12-29 21:25:51 UTC
I sometimes use "Suspend to RAM" (from the K menu).

Recently, I often experience that after resume the screen is black and there is only the mouse cursor available (which is themed the same way as in Plasma). No known Plasma key seems to work. Ctrl+Alt+F1..F12 works.

I used Ctrl+Alt+Back,Back to get a fresh login.

Setup: laptop with lid always closed and external monitor as primary screen.

Maybe related: https://bugs.kde.org/show_bug.cgi?id=349482, https://bugs.kde.org/show_bug.cgi?id=353975
Comment 1 Simone Gaiarin 2016-08-09 19:26:15 UTC
Same problem here. To me it happens on a single screen (the laptop screen) when using a multimonitor configuration.

The panel is on the external monitor, which is set as primary.

Resuming from sleep causes the laptop screen to be black, and impossible to interact with. The screen is on, and I can see the mouse cursor. The external monitor works just fine.

How can I provide more debugging information?

Running plasma 5.7.3

Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
           Display Server: X.Org 1.17.4 driver: intel Resolution: 1920x1080@60.02hz, 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 12.0.1
Comment 2 Simone Gaiarin 2016-08-09 19:32:27 UTC
I forget to say, that a workaround is to restart plasma.
Comment 3 slartibart70 2016-08-17 14:54:49 UTC
Same here with a desktop system running a nvidia gt560 card with latest binary drivers. Multi-monitor setup on hdmi and dvi ports.
Suspend and resume system, you get a black screen on both monitors with a themed mouse cursor. You can move the mouse between monitors, but no login banner is shown. Alt-ctrl F2 is giving a login prompt and then you can kill plasma (e.g. killall -u username)
Very unsatisfying....
Comment 4 slartibart70 2016-08-17 14:57:02 UTC
Forgot to mention: fedora23, latest updates from testing repo, plasma 5.7 and kde frameworks 5.25
Comment 5 Alexander Mentyu 2017-11-27 07:30:26 UTC
Somehow related to this one?:

https://bugs.kde.org/show_bug.cgi?id=386035

https://bugs.kde.org/show_bug.cgi?id=359602
Comment 6 Milton Hagler 2018-09-04 03:22:55 UTC
Same issue here with resuming from suspend results intermittently in a blank screen. The mouse cursor is visible and moves, but the screen is black although it appears to be back lit. I am running a Lenovo T480S with,

Processer:Intel Core I7-8650U
Graphics: Intel Graphics 620
OS: Ubuntu 18.04, KDE Plasma 5.12.6, 64-bit
Kernel: 4.15.0-33-generic
KDE Framework: 5.44.0
Qt: 5.95

The issue seems to arise when I resume the computer from location to another. For example: suspended at home, resumed at work. Which makes me think it is related to a change in network connections. I have never seen this happen when the computer is suspended and resumed in the same location attached to the same network. 

Previously, I thought it was related to Nvidia graphics on my previous machine, however the same issue has been happening on my current machine with only Intel graphics. 

A month or so ago I commented on another similar bug, but am unable to find the posting. Sorry for the duplication.
Comment 7 Nate Graham 2021-03-19 20:11:45 UTC
Is anyone still experiencing this in Plasma 5.21?
Comment 8 Simone Gaiarin 2021-03-20 16:11:59 UTC
Not happening to me anymore.
Comment 9 Nate Graham 2021-03-20 19:51:20 UTC
Cool, let's call it fixed.