Since the update from 2025-08-11 I noticed my plasma desktop and all open apps, keeps crashing if I use my KVM switch. I love to listen to music and I use my personal PC for that. I found out it’s because of the wayland desktop session! If I use the x11 desktop session it doesn’t crash and works like intended. Does anyone have a fix for the wayland session? It worked fine before july…
System information
System:
Kernel: 6.12.44-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
Desktop: KDE Plasma v: 6.3.6 Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-E GAMING v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 4408
date: 10/27/2022
CPU:
Info: 12-core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+
rev: 0 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB
Speed (MHz): avg: 3651 min/max: 550/4951 boost: enabled cores: 1: 3651
2: 3651 3: 3651 4: 3651 5: 3651 6: 3651 7: 3651 8: 3651 9: 3651 10: 3651
11: 3651 12: 3651 13: 3651 14: 3651 15: 3651 16: 3651 17: 3651 18: 3651
19: 3651 20: 3651 21: 3651 22: 3651 23: 3651 24: 3651 bogomips: 177336
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT
/ 6900 XT] driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 0d:00.0
Device-2: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
type: USB bus-ID: 5-1.4.2:32
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8 driver: X:
loaded: amdgpu dri: radeonsi gpu: amdgpu resolution: 1: N/A 2: N/A
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms:
active: gbm,x11,surfaceless,device inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.1-arch1.4
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6800 XT (radeonsi
navi21 LLVM 20.1.8 DRM 3.61 6.12.44-3-MANJARO)
API: Vulkan v: 1.4.321 drivers: radv surfaces: N/A devices: 1
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
driver: snd_hda_intel v: kernel bus-ID: 0d:00.1
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 0f:00.4
Device-3: Cambridge Silicon Radio CSRA64210 [TaoTronics Headset BH-22 in
charging mode] driver: hid-generic,snd-usb-audio,usbhid type: USB
bus-ID: 1-3:2
Device-4: C-Media USB Audio Device
driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 5-1.1.1:6
Device-5: Corsair VIRTUOSO SE Wireless Gaming Headset
driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 5-1.4.1:31
Device-6: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
type: USB bus-ID: 5-1.4.2:32
API: ALSA v: k6.12.44-3-MANJARO status: kernel-api
Server-1: sndiod v: N/A status: off
Server-2: PipeWire v: 1.4.7 status: active
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 05:00.0
IF: wlp5s0 state: down mac: <filter>
Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
port: e000 bus-ID: 06:00.0
IF: enp6s0 state: up speed: 2500 Mbps duplex: full mac: <filter>
Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
port: d000 bus-ID: 07:00.0
IF: enp7s0 state: down mac: <filter>
IF-ID-1: br-0a335d8d225c state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
IF-ID-3: virbr0 state: down mac: <filter>
IF-ID-4: virbr1 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB bus-ID: 1-6:4
Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
Local Storage: total: 3.64 TiB used: 1.03 TiB (28.3%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
temp: 58.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
temp: 61.9 C
ID-3: /dev/sda vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB
type: USB
Partition:
ID-1: / size: 847.54 GiB used: 570.76 GiB (67.3%) fs: ext4
dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 299.4 MiB used: 304 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: partition size: 69.07 GiB used: 1.43 GiB (2.1%)
dev: /dev/nvme0n1p3
Sensors:
System Temperatures: cpu: 54.0 C mobo: 51.0 C gpu: amdgpu temp: 57.0 C
Fan Speeds (rpm): fan-1: 1097 fan-2: 927 fan-3: 716 fan-4: 0 fan-5: 0
fan-6: 0 gpu: amdgpu fan: 664
Info:
Memory: total: 64 GiB note: est. available: 62.7 GiB used: 16.32 GiB (26.0%)
Processes: 562 Uptime: 14h 35m Init: systemd
Packages: 2201 Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Zsh v: 5.9
inxi: 3.3.39
I’d suggest running journalctl --follow and watching what appears in it at the time of the problem. This may give you some clues. It may be worth teeing it into a file so you can analyse it more easily.
2 Likes
BG405
10 September 2025 21:05
3
@XTREEMRAGE I’ve moved your post and the good reply into its own dedicated topic; especially since it references an earlier update.
Hope this will get better (dedicated) attention for you.
1 Like
I’m a linux noob, but is this what you wanted? If couldnt add the full log
sep 12 06:52:16 pc bluetoothd[1512]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
sep 12 06:52:16 pc dbus-broker-launch[1251]: Activation request for 'org.freedesktop.ModemManager1' failed.
sep 12 09:08:26 pc systemd-coredump[29046]: Process 2726 (kwin_wayland) of user 1000 dumped core.
Stack trace of thread 2726:
#0 0x00007f8812af9732 n/a (libkwin.so.6 + 0x4f9732)
#1 0x00007f880e392ac6 n/a (libffi.so.8 + 0x7ac6)
#2 0x00007f880e38f76b n/a (libffi.so.8 + 0x476b)
#3 0x00007f880e39206e ffi_call (libffi.so.8 + 0x706e)
#4 0x00007f8810d14532 n/a (libwayland-server.so.0 + 0x6532)
#5 0x00007f8810d19d30 n/a (libwayland-server.so.0 + 0xbd30)
#6 0x00007f8810d18182 wl_event_loop_dispatch (libwayland-server.so.0 + 0xa182)
#7 0x00007f8812b05b9a _ZN4KWin7Display14dispatchEventsEv (libkwin.so.6 + 0x505b9a)
#8 0x00007f880fdd37ef n/a (libQt6Core.so.6 + 0x1d37ef)
#9 0x00007f880fdddb40 _ZN15QSocketNotifier5eventEP6QEvent (libQt6Core.so.6 + 0x1ddb40)
#10 0x00007f8811101c70 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x101c70)
#11 0x00007f880fd68118 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x168118)
#12 0x00007f880ff26629 _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt6Core.so.6 + 0x326629)
#13 0x00007f880ff273c7 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3273c7)
#14 0x00007f8810b1ad33 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x71ad33)
#15 0x00007f880fd744b6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1744b6)
#16 0x00007f880fd6c7c1 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x16c7c1)
#17 0x000056092baaf569 n/a (/usr/bin/kwin_wayland + 0x40569)
#18 0x00007f880f427675 n/a (libc.so.6 + 0x27675)
#19 0x00007f880f427729 __libc_start_main (libc.so.6 + 0x27729)
#20 0x000056092bab5ba5 n/a (/usr/bin/kwin_wayland + 0x46ba5)
Stack trace of thread 2763:
#0 0x00007f880f49f042 n/a (libc.so.6 + 0x9f042)
#1 0x00007f880f4931ac n/a (libc.so.6 + 0x931ac)
#2 0x00007f880f4931f4 n/a (libc.so.6 + 0x931f4)
#3 0x00007f880f50da36 ppoll (libc.so.6 + 0x10da36)
#4 0x00007f880e7b6e04 n/a (libglib-2.0.so.0 + 0x5fe04)
#5 0x00007f880e7b6ee5 g_main_context_iteration (libglib-2.0.so.0 + 0x5fee5)
#6 0x00007f881003c5e2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x43c5e2)
#7 0x00007f880fd744b6 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1744b6)
#8 0x00007f880fe873c6 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2873c6)
#9 0x00007f8810daadae n/a (libQt6DBus.so.6 + 0x37dae)
#10 0x00007f880ff1ee69 n/a (libQt6Core.so.6 + 0x31ee69)
#11 0x00007f880f4969cb n/a (libc.so.6 + 0x969cb)
#12 0x00007f880f51aa0c n/a (libc.so.6 + 0x11aa0c)
Stack trace of thread 2783:
#0 0x00007f880f49f042 n/a (libc.so.6 + 0x9f042)
#1 0x00007f880f4931ac n/a (libc.so.6 + 0x931ac)
#2 0x00007f880f49381c n/a (libc.so.6 + 0x9381c)
#3 0x00007f880f495ede pthread_cond_wait (libc.so.6 + 0x95ede)
#4 0x00007f880196455e n/a (libgallium-25.2.1-arch1.4.so + 0x56455e)
#5 0x00007f880191de7d n/a (libgallium-25.2.1-arch1.4.so + 0x51de7d)
#6 0x00007f880196448d n/a (libgallium-25.2.1-arch1.4.so + 0x56448d)
#7 0x00007f880f4969cb n/a (libc.so.6 + 0x969cb)
#8 0x00007f880f51aa0c n/a (libc.so.6 + 0x11aa0c)
...
░░ Subject: Process 29139 (plasmashell) dumped core
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ Documentation: man:core(5)
░░
░░ Process 29139 (plasmashell) crashed and dumped core.
░░
░░ This usually indicates a programming error in the crashing program and
░░ should be reported to its vendor as a bug.
Olli
12 September 2025 07:27
5
yes this is still a problem that a lot of software must be adopted to wayland. especially all kinds of remote-software still need x-11.
p.s.: i’m using barrier as software-driven kvm-switch. a similar app as barrier is “input-leap” that should be usable with wayland (i haven’t tested it).
Well it worked before with wayland for me, that some apps will crash ok, but not the entire desktop/apps
Certainly a single application shouldn’t crash the desktop. It sounds like something that’s been introduced recently from what you say. I’d suggest raising a bug upstream for kwin_wayland, including the stack trace.
Do you have a direct link for me? Tried to google it, but don’t where I can I file it correctly.
Your problem sounds similar to an existing KDE bug, which says it is fixed in 6.4.5. You could wait to see if this fix works for you in that version, or if you do want to raise a bug report this link should point you to the correct area to do that:
https://bugs.kde.org/show_bug.cgi?id=504959
Thanks looks very similar! Because it only crashes when I switch inputs… I will wait to see if that fix it for me.
1 Like
You might need to switch to Unstable branch if you want to test it on Plasma 6.4.5. Stable & Testing branches could remain on Plasma 6.3 until Plasma 6.5 is released next month:
Plasma 6.4.5 is scheduled for Tue 2025-09-09. Plasma 6.5.0 for Tue 2025-10-21 followed by 6.5.1 on Tue 2025-10-28. After that 6.5.2 is expected on Tue 2025-11-04. The last release of 6.4 series is scheduled for on Tue 2025-11-11 as 6.4.6.
When we look at GNOME we will have 49.0 on 2025-09-17 and 49.1 on 2025-10-11.
To plan a new release of Manjaro as the distribution, we have to consider on what we want to provide, which new desktop environments we introduce and when. Zetar is focused on Plasm…
To switch to Unstable branch:
sudo pacman-mirrors --api --set-branch unstable
After you changed the branch, rebuild the mirrorlist and update your packages:
sudo pacman-mirrors --continent && sudo pacman -Syu
1 Like
.