You are not logged in.
Pages: 1
kwin_wayland crashes after updating from 6.6.5 to 6.7 beta1 (6.6.90) for testing. Works fine if I go back to 6.6.5. X11 session works on 6.7 beta1. How should I provide the journal?
Offline
https://wiki.archlinux.org/title/List_o … n_services
Mod note: moving to testing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Not sure what the actual issue was, but the issue seems to be fixed in 6.7 beta 2.
Edited to add the journal from it failing on beta 1:
https://paste.c-net.org/SwordSquashed
Last edited by oddball33 (2026-05-28 21:07:20)
Offline
And it is happening again running
Operating System: Arch Linux
KDE Plasma Version: 6.7.0
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
I have core-testing and extra-testing repos enabled, but not kde-unstable. X11 session works fine. It might not actually be kwin itself, I'm not sure.
Edited to add the journal:
https://paste.c-net.org/AheadDentist
Last edited by oddball33 (2026-06-18 14:27:54)
Offline
Jun 18 09:23:27 Johnny5 kernel: evdi: [I] (card0) Opened by Task 1407 (kwin_wayland) of process 1407 (kwin_wayland)
Jun 18 09:23:27 Johnny5 kwin_wayland[1407]: Failed to open drm node: ""
Jun 18 09:23:27 Johnny5 kwin_wayland[1407]: couldn't find dev node for drm device
Jun 18 09:23:27 Johnny5 kwin_wayland_wrapper[1407]: MESA-LOADER: failed to retrieve device informationJun 18 09:23:30 Johnny5 kernel: llvmpipe-0[1711]: segfault at e00 ip 00007fba2402d8d9 sp 00007fb9f8ff8400 error 6 likely on CPU 18 (core 30, socket 0)
Jun 18 09:23:30 Johnny5 kernel: Code: 61 e3 c5 f1 69 cb c5 e9 61 d8 c5 e9 69 c0 c5 d9 6c d1 c5 d9 6d c9 c5 e1 6c e0 c5 e1 6d c0 8d 14 00 48 63 d2 8d 34 40 48 63 f6 <c5> f9 7f 11 c5 f9 7f 0c 01 c5 f9 7f 24 11 c5 f9 7f 04 31 48 8d 65
Jun 18 09:23:30 Johnny5 systemd-coredump[1850]: Process 1669 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Jun 18 09:23:30 Johnny5 systemd[1]: Started Process Core Dump (PID 1850/UID 0).
Jun 18 09:23:30 Johnny5 systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Jun 18 09:23:30 Johnny5 systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.kameleon.qmk.helper.
Jun 18 09:23:30 Johnny5 systemd[1]: Started dbus-:1.2-org.kde.kameleon.qmk.helper@0.service.
Jun 18 09:23:30 Johnny5 NetworkManager[894]: <info> [1781792610.8130] agent-manager: agent[c15d6c8f7e8608fb,:1.41/org.kde.plasma.networkmanagement/1000]: agent registered
Jun 18 09:23:30 Johnny5 kded6[1628]: QDBusObjectPath: invalid path "/modules/wpad-detector"
Jun 18 09:23:30 Johnny5 kded6[1628]: The kded module name "wpad-detector" is invalid!
Jun 18 09:23:31 Johnny5 systemd-coredump[1852]: Process 1669 (kwin_wayland) of user 1000 dumped core.
Stack trace of thread 1718:
#0 0x00007fba2402d8d9 n/a (n/a + 0x0)
#1 0x00007fba31372bed n/a (libgallium-26.1.3-arch1.1.so + 0x972bed)
#2 0x00007fba31372d2b n/a (libgallium-26.1.3-arch1.1.so + 0x972d2b)
#3 0x00007fba31372721 n/a (libgallium-26.1.3-arch1.1.so + 0x972721)
#4 0x00007fba31372af4 n/a (libgallium-26.1.3-arch1.1.so + 0x972af4)
#5 0x00007fba31371a9c n/a (libgallium-26.1.3-arch1.1.so + 0x971a9c)
#6 0x00007fba31371bbe n/a (libgallium-26.1.3-arch1.1.so + 0x971bbe)
#7 0x00007fba3102e78d n/a (libgallium-26.1.3-arch1.1.so + 0x62e78d)
#8 0x00007fba40e981b9 n/a (libc.so.6 + 0x981b9)
#9 0x00007fba40f1d21c n/a (libc.so.6 + 0x11d21c)Jun 18 09:22:04 Johnny5 kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
Jun 18 09:22:04 Johnny5 kernel: nvidia 0000:01:00.0: [drm] No compatible format found
Jun 18 09:22:04 Johnny5 kernel: nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
Jun 18 09:22:05 Johnny5 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Removing device
Jun 18 09:22:05 Johnny5 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Unloading driver
Jun 18 09:22:06 Johnny5 systemd[1]: Starting NVIDIA Persistence Daemon...
Jun 18 09:22:06 Johnny5 nvidia-persistenced[803]: Started (803)
Jun 18 09:22:06 Johnny5 nvidia-persistenced[803]: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 143 has read and write permissions for those files.Jun 18 09:22:06 Johnny5 kernel: evdi: [I] (card0) Opened by Task 987 (Xorg.wrap) of process 987 (Xorg.wrap)
Jun 18 09:22:06 Johnny5 kernel: evdi: [I] (card0) Closed by Task 987 (Xorg.wrap) of process 987 (Xorg.wrap)
Jun 18 09:22:06 Johnny5 kernel: evdi: [I] (card0) Opened by Task 987 (Xorg) of process 987 (Xorg)You're also somehow using evdi ie. displaylink?
And
Jun 18 09:22:08 Johnny5 systemd-logind[800]: New session 'c1' of user 'sddm' with class 'greeter' and type 'x11'.
Jun 18 09:23:25 Johnny5 systemd-logind[800]: New session '2' of user 'dug' with class 'user' and type 'wayland'.SDDM (works?) runs on X11, but plasma is a wayland session, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General
Hybrid graphics, can you disable the nvidia GPU in the UEFI to check whether the troubles are coming from there?
Offline
Seth, you are a freaking genius. Long story short, disabling displaylink fixed my problem, at least for now. That's for my dock to run extra external monitors.
I normally use plasmaloginmanager, not SDDM, but it was crashing, hence using SDDM. plasma Wayland session would not run from SDDM, hence temporarily using the X11 session, so I could actually do some work.
The UEFI won't let me disable the Nvidia GPU.
Xorg log:
https://paste.c-net.org/BananasSwell
Edited to add: Thank you!
Last edited by oddball33 (2026-06-18 16:56:20)
Offline
If disabling displaylink works the problem is likely that it shows up as card0 and kwin tries to use it as primary device or at all.
=> https://wiki.archlinux.org/title/KDE#Me … -specific) might help you out here.
Offline
Pages: 1