Bug 418764 - Sometimes after resume, screen is blank with only the mouse cursor？
Summary: Sometimes after resume, screen is blank with only the mouse cursor？
Status: RESOLVED DUPLICATE of bug 347772
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: greeter (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-12 03:09 UTC by talentlcy
Modified: 2020-04-15 03:11 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description talentlcy 2020-03-12 03:09:14 UTC 
So as the title says, once every couple of days, after I resume from suspend, the screen is blank with only the mouse cursor visible. The cursor can be moved around but that's it. I'm on KDE neon user 5.18.2 and graphics card is Nvidia GTX1060.

Currently the only way to get back into the system has been to use `sudo pkill X` but this obviously kills my session and all running programs.

Do others have this issue? Is there a way to recover the session?

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon user
(available in About System)
KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Comment 1 Patrick Silva 2020-03-12 10:33:13 UTC 
*** Bug 418773 has been marked as a duplicate of this bug. ***
Comment 2 talentlcy 2020-03-12 10:59:01 UTC 
Will it be related to memory consumption? My computer's setup is 16GB RAM, and I allot 8GB for Swapfile. I noticed that it mostly happened when I was running some high memory consumption applications such as vmware machines and docker containers and coding IDE, which would comsumed all the memory, and took about 2GB of Swap space.
Comment 3 talentlcy 2020-04-01 20:18:23 UTC 
It happend again.  But this time , I loged into tty by Ctrl+Alt+F2 ,  and Found a process `kscreenlocker` using a lot of CPU, killed it then return to the lock screen by Ctrl+Alt+F1,  and successfully get back into the system.
Comment 4 Christoph Feck 2020-04-09 20:15:57 UTC 
Could be a duplicate of bug 347772 then.
Comment 5 Nate Graham 2020-04-15 03:11:49 UTC 
Yup, looks like the same.

*** This bug has been marked as a duplicate of bug 347772 ***