After the latest set of updates to KDE Neon, the password prompt does not appear immediately on the unlock screen.
I am working on a desktop computer and the screen gets automatically locked after a certain period of inactivity. When I move my mouse again, the unlock screen appears with time but not the password prompt. I need to wait good 30 seconds before the prompt for password appears. I am using X11. Does anyone know what’s going on and how I can fix it?
Hi! Once you are able to unlock the screen, it might help to check the system journal to see if there are any errors or warnings from the time that the issue was occurring.
Something like sudo journalctl --since=-5m would give you the prior five minutes’ worth of journal entries - ones that involve kscreenlocker, or anything authentication-related, might be clues about what’s going on.
(Just in case it might be relevant…does this happen if you manually trigger your screen to be locked, instead of it happening because of inactivity?)
It’ll also help with further guidance from folks here to post your basic system information from the Info Center app (using the Copy Details button is the easiest way to grab it):
Thanks @johnandmegh
Going backwards from bottom to top, the answers to your questions –
post your basic system information from the Info Center app
Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-50-generic (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D13
System Version: 1.0
does this happen if you manually trigger your screen to be locked, instead of it happening because of inactivity?
No, this does not happen if I manually lock (using shortcut Super+L) and immediately try to log back in. I did not try manually locking the screen, walking away for a little while and see if that replicates this behavior.
check the system journal to see if there are any errors or warnings from the time that the issue was occurring.
Good point! I will let it go to sleep on its own and get back to you.
Here’s what I see from the logs
Dec 14 08:41:34 cistron sh[104658]: [Parent 104658, IPC I/O Parent] WARNING: process 256116 is a zombie: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:245
Dec 14 08:41:35 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:41:35 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:42:04 cistron sh[104658]: [Parent 104658, IPC I/O Parent] WARNING: process 256198 is a zombie: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:245
Dec 14 08:42:05 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:42:05 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:42:09 cistron sh[104658]: [Parent 104658, IPC I/O Parent] WARNING: process 256143 is a zombie: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:245
Dec 14 08:42:21 cistron kscreenlocker_greet[255674]: pam_kwallet5(kde-smartcard:auth): pam_kwallet5: pam_sm_authenticate
Dec 14 08:42:21 cistron kscreenlocker_greet[255674]: pam_kwallet5(kde-smartcard:auth): pam_kwallet5: we were already executed
Dec 14 08:42:21 cistron kscreenlocker_greet[255674]: QRhiGles2: Context is lost.
Dec 14 08:42:21 cistron kscreenlocker_greet[255674]: Graphics device lost, cleaning up scenegraph and releasing RHI
Dec 14 08:42:21 cistron dbus-daemon[1354]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.4806' (uid=1000 pid=255674 comm="/lib/x86_64-linux-gnu/>
Dec 14 08:42:21 cistron systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Dec 14 08:42:21 cistron dbus-daemon[1354]: [system] Successfully activated service 'net.reactivated.Fprint'
Dec 14 08:42:21 cistron systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Dec 14 08:42:21 cistron kscreenlocker_greet[255674]: pam_kwallet5(kde-fingerprint:auth): pam_kwallet5: pam_sm_authenticate
Dec 14 08:42:21 cistron kscreenlocker_greet[255674]: pam_kwallet5(kde-fingerprint:auth): pam_kwallet5: we were already executed
Dec 14 08:42:32 cistron kscreenlocker_greet[255674]: QRhiGles2: Context is lost.
Dec 14 08:42:32 cistron kscreenlocker_greet[255674]: Failed to create RHI (backend 2)
Dec 14 08:42:33 cistron kscreenlocker_greet[255674]: QRhiGles2: Context is lost.
Dec 14 08:42:33 cistron kscreenlocker_greet[255674]: Graphics device lost, cleaning up scenegraph and releasing RHI
Dec 14 08:42:33 cistron kscreenlocker_greet[255674]: QRhiGles2: Context is lost.
Dec 14 08:42:33 cistron kscreenlocker_greet[255674]: Failed to create RHI (backend 2)
Dec 14 08:42:34 cistron sh[104658]: [Parent 104658, IPC I/O Parent] WARNING: process 256248 is a zombie: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:245
Dec 14 08:42:35 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:42:35 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:42:37 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:42:37 cistron rtkit-daemon[1769]: Supervising 12 threads of 9 processes of 1 users.
Dec 14 08:42:40 cistron kscreenlocker_greet[255674]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate
Dec 14 08:42:40 cistron kscreenlocker_greet[255674]: pam_kwallet5(kde:auth): pam_kwallet5: we were already executed
Dec 14 08:42:40 cistron kscreenlocker_greet[255674]: pam_kwallet5(kde:setcred): pam_kwallet5: pam_sm_setcred
There were a few rows with sshd that I thought were not relevant so I removed them for clarity.
Ah, this looks like a known bug with X11 and AMD or Nvidia GPUs then: 483094 – On X11 with AMD or NVIDIA GPU, after monitor wake-up, unlocking the screen is delayed by 30-60 seconds
Depending on your setup, you might be able to workaround this by using a Wayland session instead?
Ah, this looks like a known bug with X11 and AMD or Nvidia GPUs
Yup, that’s the one. And I too can confirm that this is an issue only when the machine goes to sleep after inactivity. If I manually lock the screen before walking away from the machine, the password prompt appears as usual.
Depending on your setup, you might be able to workaround this by using a Wayland session instead?
I was using Wayland until the latest updates screwed that up too 
If I try to log into a Wayland session, the screen goes blank and nothing happens. All I see is a mouse pointer on a black screen no matter how long I wait.
Yeah, unfortunately Neon users seem to have run into several graphics driver-related issues recently - I believe largely driven by the challenge of keeping quickly-moving desktop software up-to-date on top of an underlying base system that intentionally does not move its versions/features forward (Ubuntu 24.04 LTS).
Based on comment #22 there, it might be helpful for the bug report investigation to contribute a comment of your own mentioning whether the problem occurs on your system using the Nouveau drivers, or if it only occurs for you with the proprietary Nvidia ones.
Thanks,
Thanks, I can’t figure out how to switch to nouveau drivers. I tried completely removing the nvidia drivers but that did not help.
Now I see the following:
$ inxi -SG
System:
Host: cistron Kernel: 6.8.0-50-generic arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.2.4 Distro: KDE neon 24.04 6.2 noble
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060] driver: nvidia v: 560.35.03
Device-2: Logitech C920 PRO HD Webcam driver: snd-usb-audio,uvcvideo
type: USB
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: nouveau unloaded: fbdev,modesetting,vesa failed: nvidia
gpu: nvidia,nvidia-nvswitch resolution: 1: 1920x1080~60Hz
2: 1920x1080~60Hz
API: EGL v: 1.5 drivers: kms_swrast,nvidia,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 560.35.03
renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib
What I don’t understand is this part:
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: nouveau unloaded: fbdev,modesetting,vesa failed: nvidia
Does that mean I am using nvidia drivers or nouveau driver? Why does it list nvidia under failed?
I wondered if nouveau needs to be blacklisted. So, I created the file /etc/modprobe.d/blacklist-nvidia-nouveau.conf with the following contents:
$ cat /etc/modprobe.d/blacklist-nvidia-nouveau.conf
blacklist nouveau
options nouveau modeset=0
A sudo update-initramfs -u followed by a system restart did not make any difference; I still see nouveau as ‘loaded’ and nvidia as ‘failed’.
Just checking, are you using the Ubuntu Drivers utility (https://ubuntu.com/server/docs/nvidia-drivers-installation) to manage the Nvidia drivers? When I was on Ubuntu I found it to be more reliable than the manual package manager installation methods, so if you’re not using that already, it might be worth a try.
(And if you aren’t able to readily swap out the Nvidia driver for Nouveau to add to that bug report - that’s less of a big deal at this point, I think, than just making sure you have your system running!)
Yes, that’s what I am using.