SUMMARY I am getting kscreenlocker failing rather regularly on my desktop (AMD GPU) system. Intel GPU laptop haven't reproduced. I used to get this on occasion if I say upgraded to a new Plasma release in the 5.x days and didn't reboot. This seems different and unrelated to upgrading my system. I've included the journalcrtl log which starts with a seg fault in eglSwapBuffers. Doesn't happen all the time, but happens enough that it is pretty annoying (and effectively locks the better half/others out of the computer as they don't really know what a virtual terminal is). STEPS TO REPRODUCE 1. Lock Screen 2. Sleep computer 3. Wake Computer OBSERVED RESULT Quite often the lock screen presents the broken screen requesting to drop to virtual terminal to unlock EXPECTED RESULT Lock screen should be shown SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.2-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT ADDITIONAL INFORMATION Here is what I can find in journalcrtl: Apr 05 10:13:24 desktop kscreenlocker_greet[122558]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 Apr 05 10:13:24 desktop kernel: kscreenlocker_g[122558]: segfault at 647500000076 ip 00007dc46da45c4c sp 00007fff90b0f380 error 4 in libPlasmaQuick.so.6.0.3[7dc46da1f000+50000] likely on CPU 18 (core 8, socket 0) Apr 05 10:13:24 desktop kernel: Code: 1e fa 48 8b 47 28 48 8b 78 08 ff 25 a6 58 04 00 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 48 83 ec 08 48 8b 47 28 <48> 8b 78 08 ff 15 1a 6a 04 00 48 85 c0 74 11 48 8b 50 08 f6 42 31 Apr 05 10:13:24 desktop kwin_wayland_wrapper[97857]: not a valid new object id (2), message get_registry(n) Apr 05 10:13:24 desktop kwin_wayland_wrapper[97857]: error in client communication (pid 97857) Apr 05 10:13:24 desktop kwin_wayland_wrapper[122896]: wl_display@1: error 1: invalid arguments for wl_display@1.get_registry Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: qt.qpa.wayland: Loading shell integration failed. Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: qt.qpa.wayland: Attempted to load the following shells QList("layer-shell") Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. Apr 05 10:13:24 desktop kscreenlocker_greet[122896]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: xcb, linuxfb, minimalegl, vnc, eglfs, offscreen, minimal, wayland-egl, wayland, vkkhrdisplay. Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: qt.qpa.wayland: Loading shell integration failed. Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: qt.qpa.wayland: Attempted to load the following shells QList("layer-shell") Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. Apr 05 10:13:24 desktop kscreenlocker_greet[122900]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: xcb, linuxfb, minimalegl, vnc, eglfs, offscreen, minimal, wayland-egl, wayland, vkkhrdisplay. Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: qt.qpa.wayland: Loading shell integration failed. Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: qt.qpa.wayland: Attempted to load the following shells QList("layer-shell") Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. Apr 05 10:13:24 desktop kscreenlocker_greet[122903]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: xcb, linuxfb, minimalegl, vnc, eglfs, offscreen, minimal, wayland-egl, wayland, vkkhrdisplay. Apr 05 10:13:24 desktop plasmashell[98084]: The cached device pixel ratio value was stale on window expose. Please file a QTBUG which explains how to reproduce.
I have a similar problem also using AMD GPU. On Plasma 5 this happened only occasionally, but now with Plasma 6 I already had this 2 times in just two days after the upgrade. I also see the error message about broken lock screen requesting me to do "loginctl unlock-session 2" in a separate session. I will attach my journal logs. My system's details: Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.6.30-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6800 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B46 System Version: 1.0
Created attachment 169505 [details] Journal logs
I have EXACTLY the same problem. I have 3 monitors, the center one doesn't wake up from sleep, I have to unplug the power chord and plug it again. It started happening yesterday, after the Manjaro big update, which updated KDE to the latest version. I'm using NVIDIA proprietary drivers.
Getting the same issue with resume from sleep on my laptop; I have a thunderbolt dock with two monitors running off the dock. Have the same eglSwapBuffers failed error followed by a kernel trap. Doesn't happen consistently :| Laptop has an intel iGPU Have also observed on my desktop when resuming from sleep and forgot to switch my kvm over; meaning it would have resumed with no monitors attached. Desktop uses nvidia proprietary drivers (version 550). Software versions observed on: KDE Plasma 6.0.4 & 6.0.5 KDE Frameworks 6.2.0 QT 6.7.0 & 6.7.1 Linux Kernel: 6.8.9, 6.8.10, 6.9.0, 6.9.1
Created attachment 169787 [details] Boot from suspend log - sanitized Log of boot up from suspend, replugged thunderbolt dock after "seeing SDDM crashed switch to vterm 1 to login" message.
Same here on Plasma 6.1 Beta Operating System: KaOS (2024) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-1 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Product Name: NUC12WSHi5 plasmashell[1146]: qml: Connection lost kernel: kscreenlocker_g[7309]: segfault at 62 ip 00007f64e898da2a sp 00007ffcc2ec38f0 error 4 in libPlasmaQuick.so.6.0.90[7f64e8959000+60000] likely on CPU 2 (core 4, socket 0) kernel: Code: 48 8b 47 28 48 8b 78 08 e9 83 bb fc ff 90 66 90 48 83 ec 08 48 8b 47 28 48 8b 78 08 e8 0f d8 fc ff 48 85 c0 74 11 48 8b 50 08 <f6> 42 31 01 ba 00 00 00 00 48 0f 44 c2 48 83 c4 08 c3 0f 1f 40 00 kwin_wayland_wrapper[1026]: not a valid new object id (2), message get_registry(n) kwin_wayland_wrapper[1026]: error in client communication (pid 1026) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (49) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (50) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (47) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (42) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (46) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (38) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (25) kwin_wayland_wrapper[7478]: error: received delete_id for unknown id (24) kwin_wayland_wrapper[7478]: wl_display@1: error 1: invalid arguments for wl_display@1.get_registry kscreenlocker_greet[7478]: qt.qpa.wayland: Loading shell integration failed. kscreenlocker_greet[7478]: qt.qpa.wayland: Attempted to load the following shells QList("layer-shell") kscreenlocker_greet[7478]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. kscreenlocker_greet[7478]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimalegl, minimal, offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland. kscreenlocker_greet[7482]: qt.qpa.wayland: Loading shell integration failed. kscreenlocker_greet[7482]: qt.qpa.wayland: Attempted to load the following shells QList("layer-shell") kscreenlocker_greet[7482]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. kscreenlocker_greet[7482]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimalegl, minimal, offscreen, vkkhrdisplay, vnc, xcb, wayland-egl, wayland.
Related to this bug, I suggest also the change the error message which asks to press CTRL+ALT+F2 because it doesn't work at least on Wayland. I must use CTRL+ALT+F3, not F2
This bug also happens on OpenBSD Plasma 6, where loginctl is not available so it can't be fixed with the CTRL+ALT+F2 trick. Since this bug report is not so active, I can suppose it's something related to some hardware or specific configuration because I get this bug on every distro I tried (KaOS/6, Kubuntu/5.27, OpenBSD/6) but most of the users don't.
I'm seeing the same problem. Archlinux, kde 6.1.0, amd ryzen 9 5900X, radeon 7600X. It seems to crash when the screensaver kicks in *and* the monitor shuts down.
Note it wasn't happening on kde 6.0.X
Is anyone affected using only one screen? Or is it only with multiple screens?
I'm using, and always used, a single monitor connected to my Intel NUC. I've never used multiple screens
(In reply to Nate Graham from comment #11) > Is anyone affected using only one screen? Or is it only with multiple > screens? I'm using dual screen. I've also got an update: with kde 6.1.1, the unlock screen works, I don't need to switch to a console, but still there are crashes. Now apparently kmail also crashes, but I'm not sure if it is related. giu 27 20:44:30 betelgeuse systemd-coredump[131031]: Process 130365 (kmail) of user 1000 terminated abnormally with signal 11/SEGV, processing... giu 27 20:44:30 betelgeuse systemd[1]: Started Process Core Dump (PID 131031/UID 0). giu 27 20:44:30 betelgeuse systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. giu 27 20:44:30 betelgeuse kernel: kscreenlocker_g[130883]: segfault at 8 ip 00007d59a31aaee4 sp 00007fffa7d681a8 error 4 in libQt6Gui.so.6.7.2[7d59a30d9000+618000] likely on CPU 10 (core 12, socket 0) giu 27 20:44:30 betelgeuse kernel: Code: 84 00 00 00 00 00 f0 83 28 01 75 9a 48 8b 7d b0 ff 15 90 87 68 00 eb 8e ff 15 80 8c 68 00 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 57 08 48 8b 02 48 85 c0 74 10 8b 40 04 85 c0 74 09 48 8b 42 giu 27 20:44:44 betelgeuse systemd-coredump[131029]: [🡕] Process 125756 (plasmashell) of user 1000 dumped core. Stack trace of thread 125879: #0 0x00007e68684a8e44 n/a (libc.so.6 + 0x94e44) #1 0x00007e6868450a30 raise (libc.so.6 + 0x3ca30) #2 0x00007e686b31b643 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6643) #3 0x00007e6868450ae0 n/a (libc.so.6 + 0x3cae0) #4 0x00007e68699a540b _ZNK15QtWaylandClient14QWaylandWindow16devicePixelRatioEv (libQt6WaylandClient.so.6 + 0x9140b) #5 0x00007e686236ff0c _ZN15QtWaylandClient17QWaylandEglWindow13updateSurfaceEb (libQt6WaylandEglClientHwIntegration.so.6 + 0x8f0c) #6 0x00007e6862370905 _ZN15QtWaylandClient17QWaylandGLContext11makeCurrentEP16QPlatformSurface (libQt6WaylandEglClientHwIntegration.so.6 + 0x9905) #7 0x00007e68694adc28 _ZN14QOpenGLContext11makeCurrentEP8QSurface (libQt6Gui.so.6 + 0x4adc28) #8 0x00007e686966f112 n/a (libQt6Gui.so.6 + 0x66f112) #9 0x00007e686a418647 n/a (libQt6Quick.so.6 + 0x418647) #10 0x00007e686a419f9a n/a (libQt6Quick.so.6 + 0x419f9a) #11 0x00007e6868cc9747 n/a (libQt6Core.so.6 + 0x2c9747) #12 0x00007e68684a6ded n/a (libc.so.6 + 0x92ded) #13 0x00007e686852a0dc n/a (libc.so.6 + 0x1160dc) Stack trace of thread 125756: #0 0x00007e68684a34e9 n/a (libc.so.6 + 0x8f4e9) #1 0x00007e68684a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9) #2 0x00007e6868cce120 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce120) #3 0x00007e686a413bd4 n/a (libQt6Quick.so.6 + 0x413bd4) #4 0x00007e686a4148bd n/a (libQt6Quick.so.6 + 0x4148bd) #5 0x00007e686a24d8de _ZN12QQuickWindowD1Ev (libQt6Quick.so.6 + 0x24d8de) #6 0x000060db1a4bea40 n/a (plasmashell + 0x3ca40) #7 0x00007e6868b8be0a _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18be0a) #8 0x00007e686aafc51c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc51c) #9 0x00007e6868b44d28 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144d28) #10 0x00007e6868b450eb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1450eb) #11 0x00007e6868da49ec n/a (libQt6Core.so.6 + 0x3a49ec) #12 0x00007e686764da89 n/a (libglib-2.0.so.0 + 0x5ca89) #13 0x00007e68676af9b7 n/a (libglib-2.0.so.0 + 0xbe9b7) #14 0x00007e686764cf95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #15 0x00007e6868da2cbd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a2cbd) #16 0x00007e6868b4f01e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f01e) #17 0x00007e6868b4934d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14934d) #18 0x000060db1a4a8d66 n/a (plasmashell + 0x26d66) #19 0x00007e6868439c88 n/a (libc.so.6 + 0x25c88) #20 0x00007e6868439d4c __libc_start_main (libc.so.6 + 0x25d4c) #21 0x000060db1a4a9255 n/a (plasmashell + 0x27255) [...] giu 27 20:44:44 betelgeuse systemd-coredump[131032]: [🡕] Process 130365 (kmail) of user 1000 dumped core. Module libintlc.so.5 without build-id. Module libimf.so without build-id. Module libirng.so without build-id. Module libsvml.so without build-id. Module libOpenCL.so.1 without build-id. Stack trace of thread 130365: #0 0x00007a6c742a8e44 n/a (libc.so.6 + 0x94e44) #1 0x00007a6c74250a30 raise (libc.so.6 + 0x3ca30) #2 0x00007a6c807d3643 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6643) #3 0x00007a6c74250ae0 n/a (libc.so.6 + 0x3cae0) #4 0x00007a6c74faaee4 _ZNK15QPlatformScreen6screenEv (libQt6Gui.so.6 + 0x1aaee4) #5 0x00007a6c6a9ab726 _ZN15QtWaylandClient14QWaylandWindow20handleScreensChangedEv (libQt6WaylandClient.so.6 + 0x97726) #6 0x00007a6c749a16f7 n/a (libQt6Core.so.6 + 0x1a16f7) #7 0x00007a6c749a16f7 n/a (libQt6Core.so.6 + 0x1a16f7) #8 0x00007a6c74feb0a1 _ZN22QWindowSystemInterface17handleScreenAddedEP15QPlatformScreenb (libQt6Gui.so.6 + 0x1eb0a1) #9 0x00007a6c6a97feea _ZN15QtWaylandClient15QWaylandDisplay23handleScreenInitializedEPNS_14QWaylandScreenE (libQt6WaylandClient.so.6 + 0x6beea) #10 0x00007a6c6a9a2e96 _ZN15QtWaylandClient14QWaylandScreen15maybeInitializeEv (libQt6WaylandClient.so.6 + 0x8ee96) #11 0x00007a6c6be80596 n/a (libffi.so.8 + 0x7596) #12 0x00007a6c6be7d00e n/a (libffi.so.8 + 0x400e) #13 0x00007a6c6be7fbd3 ffi_call (libffi.so.8 + 0x6bd3) #14 0x00007a6c6bea8860 n/a (libwayland-client.so.0 + 0x4860) #15 0x00007a6c6bea90d9 n/a (libwayland-client.so.0 + 0x50d9) #16 0x00007a6c6bea94f3 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x54f3) #17 0x00007a6c6a9740a6 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt6WaylandClient.so.6 + 0x600a6) #18 0x00007a6c7498c00f _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c00f) #19 0x00007a6c758fc51c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc51c) #20 0x00007a6c74944d28 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144d28) #21 0x00007a6c749450eb _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1450eb) #22 0x00007a6c74ba49ec n/a (libQt6Core.so.6 + 0x3a49ec) #23 0x00007a6c717dba89 n/a (libglib-2.0.so.0 + 0x5ca89) #24 0x00007a6c7183d9b7 n/a (libglib-2.0.so.0 + 0xbe9b7) #25 0x00007a6c717daf95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #26 0x00007a6c74ba2cbd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a2cbd) #27 0x00007a6c7494f01e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f01e) #28 0x00007a6c7494934d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14934d) #29 0x000064fafb263af6 n/a (kmail + 0x4af6) #30 0x00007a6c74239c88 n/a (libc.so.6 + 0x25c88) #31 0x00007a6c74239d4c __libc_start_main (libc.so.6 + 0x25d4c) #32 0x000064fafb2647c5 n/a (kmail + 0x57c5)
(In reply to Nate Graham from comment #11) > Is anyone affected using only one screen? Or is it only with multiple > screens? Happening to me with just one screen.
Addendum: I also noticed that by unlocking the session via virtual terminal also breaks the brightness control. So now i cannot press the night light and brightness icon and control the screen brightness
(In reply to Nate Graham from comment #11) > Is anyone affected using only one screen? Or is it only with multiple > screens? Seen the same thing periodically using multiple monitors - laptop screen, laptop hdmi, laptop usb-c to display link. CTRL-ALT-F2 - opens the login screen which is disabled and unusable CTRL-D - does not function Forced to do a hardware reboot. Saw similar issue occasionally in Plasma 5.27. Now more frequent. Appears to be a multiple monitor issue. Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.1.94-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 46.5 GiB of RAM Graphics Processor: AMD Radeon Graphics
This should be fixed since https://invent.kde.org/plasma/kwin/-/merge_requests/5939