This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Lock Screen hangs

Tags: None
(comma "," separated)
yodamin
Registered Member
Posts
9
Karma
0

Lock Screen hangs  Topic is solved

Tue Dec 06, 2022 11:57 am
This an issue related to sleep/hibernation and kscreen2/kwin crashing when sleep/hibernation was active for longer than 9 hours - I tested it, I put the PC to sleep and checked it after an hour, all good, then sleep and checked it after 3 hours, all good, then put it to sleep and check it after 5 hours, all good, and so on until the 9th hour -> then had to hard reboot because kwin/kscreen/plasma or one of them just hung and was not re-active to any input from keyboard or mouse. - I turned all of that sleep/hibernation **** off and that resolved the kde/plasma hanging when waking up from sleep/hibernation. BUT the ghosting icons, disappearing taskbars and multi-display arrangement and settings getting all outta wack continued.

See this post for that resolution: viewtopic.php?f=15&t=177671




Hi,

My system:

@who-r-u:~$ inxi -v 2
System:
Host: who-r-u Kernel: 5.19.0-26-generic arch: x86_64 bits: 64
Desktop: KDE Plasma v: 5.25.5 Distro: Ubuntu 22.10 (Kinetic Kudu)
Machine:
Type: Desktop System: Micro-Star product: Z370 Gaming Infinite X(MS-B916)
v: 1.0 serial: <superuser required>
Mobo: Micro-Star model: Z370M GAMING PRO AC (MS-7B44) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 9.40
date: 12/27/2017
CPU:
Info: 6-core Intel Core i7-8700K [MT MCP] speed (MHz): avg: 3233
min/max: 800/4700:5000
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1070] driver: nvidia v: 515.65.01
Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.3 driver:
X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa
gpu: nvidia,nvidia-nvswitch resolution: 1: 2560x1440 2: 2560x1440
3: 2560x1440
OpenGL: renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA
515.65.01
Network:
Device-1: Intel Ethernet I219-V driver: e1000e
Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak]
driver: iwlwifi
Drives:
Local Storage: total: 10.24 TiB used: 5.89 TiB (57.5%)
Info:
Processes: 296 Uptime: 12m Memory: 31.29 GiB used: 2.6 GiB (8.3%)
Shell: Bash inxi: 3.3.21
----------------------------------------------------------------------------------
I lock my desktop and go to bed.
I wake up and enter my password and I get a little icon that says "unlock" on it.
nothing I do from here shows any reaction on my screen. I click unlock=nothing
I bring up the virtual keyboard and type my password again=nothing
I try all three of my monitors = nothing
I ctrl+alt+F* = nothing

The ONLY thing that seems to work is power button off / on and then I can logon
I tested locking my screen for about 3-4 hours and it unlocks fine / this only happens when I have an extended lock screen, like over night
I would like to be able to tail -f something but whats the point if ctrl_alt_F* does not work and I cannot resume my current session?

Does anyone more knowledgeable than I have any suggestions on how to approach finding out whats happening and possibly fixing it?

Thanks all.


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell