SUMMARY Kde screen locker hangs when I wake my pc. I can enter my password and it unlocks but only after a couple of minutes. The login password input screen does not show. Its hung on the clock/wallpaper screen, cannot get into tty. This does not happen when I manually lock the screen with `Ctrl+Alt+L` but only when I let it to lock on its own. STEPS TO REPRODUCE 1. Let pc lock by waiting (set the timer to a smaller timeout) 2. Attempt to loging normally OBSERVED RESULT Hangs on wallpaper/clock screen. EXPECTED RESULT Should allow to input password and immediately login. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Journal logs post login: Jul 22 18:37:09 nebula kscreenlocker_greet[48741]: Graphics device lost, cleaning up scenegraph and releasing RHI Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:256: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:461: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:657: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:911: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1047: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1249: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1451: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1629: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1737: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1978: Could not add child element to parent element because the types are incorrect. Jul 22 19:26:59 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:2221: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:256: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:461: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:657: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:911: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1047: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1249: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1451: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1629: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1737: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:1978: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:00 nebula kscreenlocker_greet[62401]: qt.svg: <input>:303:2221: Could not add child element to parent element because the types are incorrect. Jul 22 19:27:04 nebula kscreenlocker_greet[62401]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB". Search paths QList("/usr/share/qt6/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") Jul 22 19:27:04 nebula kscreenlocker_greet[62401]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB". Search paths QList("/usr/share/qt6/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") Jul 22 19:37:42 nebula kscreenlocker_greet[62401]: pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-62401) opened. Jul 22 19:37:42 nebula kscreenlocker_greet[62401]: QRhiGles2: Context is lost. Jul 22 19:37:42 nebula kscreenlocker_greet[62401]: Graphics device lost, cleaning up scenegraph and releasing RHI Jul 22 19:37:58 nebula kscreenlocker_greet[62401]: QRhiGles2: Context is lost. Jul 22 19:37:58 nebula kscreenlocker_greet[62401]: Graphics device lost, cleaning up scenegraph and releasing RHI Jul 22 19:37:58 nebula kscreenlocker_greet[62401]: QRhiGles2: Context is lost. Jul 22 19:37:58 nebula kscreenlocker_greet[62401]: Failed to create RHI (backend 2)
I am using X for the graphics platform.
Can confirm similar behavior on: Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-200.fc40.x86_64 (64-bit) Graphics Platform: X11
Confirming similar behavior: Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-200.fc40.x86_64 (64-bit) Graphics Platform: X11
Can confirm similar behaviour, some details: SUMMARY for me it takes about 10 seconds for the Password prompt to show up when unlocking the screen. STEPS TO REPRODUCE It also only happens when the screen is being locked automatically, If I lock it manually with meta + L it doesn't happen. Has happened on a 3060ti as well and any Kernels. It only happens on X11, Wayland is actually fine. I'm not using wayland yet because pen monitor calibration is not implemented yet for Wayland in any form. Operating System: Arch Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.2-zen1-1-zen (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd Product Name: MS-7B86 System Version: 2.0 Video Driver: 555.58.02 Logs: Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-229412) opened. [unrelated] Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: Graphics device lost, cleaning up scenegraph and releasing RHI [unrelated] Jul 21 15:09:06 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:06 archlinux kscreenlocker_greet[229412]: Failed to create RHI (backend 2) Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: Graphics device lost, cleaning up scenegraph and releasing RHI Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: Graphics device lost, cleaning up scenegraph and releasing RHI Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: Failed to create RHI (backend 2) Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is lost. Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: Failed to create RHI (backend 2)
I am also experiencing similar issues where it only seems to occur coming from idle/wakeup state (not when manually locking) I don't see any prompt to type in, but I can type in my password and hit enter and after maybe 10+ seconds if I typed in properly it'll unlock and go back to the desktop. I've tried changing the themes around as I've seen that being a suggestion online but swapping them makes no difference and also changing the lockscreen themes makes no difference as well. SOFTWARE/OS VERSIONS: Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version 6.10.4 Graphics (X11) Hardware 4 monitors with Nvidia GeForce RTX 3080 Ti. Running the nvidia 555.58.02-15 drivers The only thing I see from journalctl around time of wakeup is ``` Aug 21 08:57:53 nemesis kscreenlocker_greet[38624]: QRhiGles2: Context is lost. Aug 21 08:57:53 nemesis kscreenlocker_greet[38624]: Graphics device lost, cleaning up scenegraph and releasing RHI Aug 21 08:57:53 nemesis kscreenlocker_greet[38624]: pam_systemd_home(kde:auth): New sd-bus connection (system-bus-pam-systemd-home-38624) opened. Aug 21 08:58:37 nemesis kscreenlocker_greet[38624]: QRhiGles2: Context is lost. Aug 21 08:58:37 nemesis kscreenlocker_greet[38624]: Failed to create RHI (backend 2) ```
(In reply to Loque from comment #4) > Can confirm similar behaviour, some details: > > SUMMARY > for me it takes about 10 seconds for the Password prompt to show up when > unlocking the screen. > > STEPS TO REPRODUCE > It also only happens when the screen is being locked automatically, If I > lock it manually with meta + L it doesn't happen. > > Has happened on a 3060ti as well and any Kernels. It only happens on X11, > Wayland is actually fine. I'm not using wayland yet because pen monitor > calibration is not implemented yet for Wayland in any form. > > > Operating System: Arch Linux > KDE Plasma Version: 6.1.3 > KDE Frameworks Version: 6.4.0 > Qt Version: 6.7.2 > Kernel Version: 6.10.2-zen1-1-zen (64-bit) > Graphics Platform: X11 > > ADDITIONAL INFORMATION > Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor > Memory: 31.3 GiB of RAM > Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2 > Manufacturer: Micro-Star International Co., Ltd > Product Name: MS-7B86 > System Version: 2.0 > > Video Driver: 555.58.02 > > Logs: > > Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: > pam_systemd_home(kde:auth): New sd-bus connection > (system-bus-pam-systemd-home-229412) opened. > [unrelated] > Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is > lost. > Jul 21 15:08:22 archlinux kscreenlocker_greet[229412]: Graphics device lost, > cleaning up scenegraph and releasing RHI > [unrelated] > Jul 21 15:09:06 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is > lost. > Jul 21 15:09:06 archlinux kscreenlocker_greet[229412]: Failed to create RHI > (backend 2) > Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is > lost. > Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: Graphics device lost, > cleaning up scenegraph and releasing RHI > Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is > lost. > Jul 21 15:09:18 archlinux kscreenlocker_greet[229412]: Graphics device lost, > cleaning up scenegraph and releasing RHI > Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is > lost. > Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: Failed to create RHI > (backend 2) > Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: QRhiGles2: Context is > lost. > Jul 21 15:09:19 archlinux kscreenlocker_greet[229412]: Failed to create RHI > (backend 2) Additional info: There is a forum thread regarding this problem. Also the problem got worse with driver version 560.35.03 , The Login Prompt doesn't show up at all anymore. https://discuss.kde.org/t/screen-locker-must-switch-to-virtual-console-and-back-to-get-password-dialog/18475/11
The same issue of Fedora 41 with plasma kscreenlocker-6.2.3-1.fc41.x86_64 Error log: Nov 15 16:47:01 pc-i7 kscreenlocker_greet[19428]: QRhiGles2: Context is lost. Nov 15 16:47:01 pc-i7 kscreenlocker_greet[19428]: Graphics device lost, cleaning up scenegraph and releasing RHI Nov 15 16:47:02 pc-i7 kscreenlocker_greet[19428]: QRhiGles2: Context is lost. Nov 15 16:47:02 pc-i7 kscreenlocker_greet[19428]: Failed to create RHI (backend 2) It looks like Bug 496290 is duplicated to this Bug.
Hi - connecting to a previously-filed bug since both appear to be based on issues with Kscreenlocker delays under X11. *** This bug has been marked as a duplicate of bug 483094 ***
Dec 03 08:14:33 pc-i7 systemd[1416]: Started app-org.kde.konsole@e92436b91af0460b9af47ee0f5e5d959.service - Konsole - Terminal. Dec 03 08:15:04 pc-i7 kded6[1750]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor" Dec 03 08:15:05 pc-i7 plasmashell[1761]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor" Dec 03 08:16:22 pc-i7 kded6[1750]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor" Dec 03 08:16:22 pc-i7 plasmashell[1761]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor" Dec 03 08:16:35 pc-i7 kscreenlocker_greet[3520]: QRhiGles2: Context is lost. Dec 03 08:16:35 pc-i7 kscreenlocker_greet[3520]: Graphics device lost, cleaning up scenegraph and releasing RHI Dec 03 08:16:35 pc-i7 kscreenlocker_greet[3520]: QRhiGles2: Context is lost. Dec 03 08:16:35 pc-i7 kscreenlocker_greet[3520]: Failed to create RHI (backend 2) It is still reproduced on: Fedora 41; kscreenlocker-6.2.4-1.fc41.x86_64