Kscreenlock freezes and plasma crashes after lockscreen

Ask Fedora
,
1

I just upgraded from Windows 11 to Fedora 43 KDE. Mostly everything works perfect but one annoying issue keeps reoccurring. When ever I lock the screen kscreenlock will become unresponsive, and will not take the password. Switching to a virt console and running loginctl unlock screen will not unlock the screen but sending a kill signal to the process will cause it to re-spawn and become responsive.

There doesn’t seem to be any pattern to this, some times I will lock it and it will immediately fall into this state and sometimes it will be fine for hours and accept the login password. I’ve done the appropriate updates and followed suggestions I’ve found on line. Nothing seems to change this behavior.

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.17.12-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i9-9900K CPU @ 3.60GHz
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4070
Manufacturer: ASUS

Running nvidia graphics drivers, latest version as of this posting.

Plasma will also crash and respawn after I get logged again. I’m not sure if this is a part of the problem or just caused by the way I have to unlock the display with the kill signal.

2

Is this the rpmfusion nvidia drivers?

3

I’m not sure. I installed them through the Discovery app. Version 580.119.02-1.fc43 is what it says there.

5

Adding to this to say I am also experiencing this issue, I also have an NVIDIA RTX 4070 (ASUS manufacturer), AMD Ryzen 3700x CPU and ASUS B550-F motherboard. I am using the RPMFusion NVIDIA drivers.

X11 is not an option for me as it messes up my multi-monitor setup.

I initially bypassed this problem by pressing Ctrl + Alt + F2-F10 (until one worked) when I was booted back to the login screen, which put me back into an authenticated session without needing to re-login.

Today I did a system update in the Discovery app which so far has made this issue go away, but for how long…? I have no clue.