Kwin_wayland crash when playing 3D game

maledict · April 8, 2026, 8:22pm

Hello,
When I load a save of Rise of the Tomb Raider with 3D stereoscopic enabled, kwin_wayland crash and so every app also crashes.
It was working fine a few days ago, so it’s either a regression or an issue that just didn’t appear last time.
I see issues about amdgpu in the logs so maybe the issue isn’t from plasma ?

DrKondi is downloading debug data since a loooong time so I will post it’s output once it’s finished.

WayVR logs :


  2026-04-08T20:08:05.060927Z  INFO wlx_capture::pipewire: DP-3: stream state changed: Paused -> Streaming
    at /home/runner/work/wayvr/wayvr/wlx-capture/src/pipewire.rs:308

radv/amdgpu: The CS has been cancelled because the context is lost. This context is innocent.
ERROR [vk_cmd_submit_locked] vkQueueSubmit: VK_ERROR_DEVICE_LOST
ERROR [vk_cmd_pool_submit_cmd_buffer_locked] vk_cmd_submit_locked: VK_ERROR_DEVICE_LOST
ERROR [submit_image_barrier] vk_cmd_pool_submit_cmd_buffer: VK_ERROR_DEVICE_LOST 4294967292
XR_ERROR_RUNTIME_FAILURE in xrReleaseSwapchainImage: Call to xrt_swapchain_barrier_image failed
  2026-04-08T20:09:54.279174Z  INFO wlx_capture::pipewire: DP-3: pipewire loop exited
    at /home/runner/work/wayvr/wayvr/wlx-capture/src/pipewire.rs:556

  2026-04-08T20:09:54.279589Z  INFO wlx_capture::pipewire: DP-3: stream state changed: Streaming -> Paused
    at /home/runner/work/wayvr/wayvr/wlx-capture/src/pipewire.rs:308

  2026-04-08T20:09:54.279867Z  INFO wlx_capture::pipewire: DP-3: stream state changed: Paused -> Unconnected
    at /home/runner/work/wayvr/wayvr/wlx-capture/src/pipewire.rs:308

  2026-04-08T20:09:54.281149Z  INFO wlx_capture::pipewire: HDMI-A-1: pipewire loop exited
    at /home/runner/work/wayvr/wayvr/wlx-capture/src/pipewire.rs:556

  2026-04-08T20:09:54.281210Z  INFO wlx_capture::pipewire: HDMI-A-1: stream state changed: Paused -> Unconnected
    at /home/runner/work/wayvr/wayvr/wlx-capture/src/pipewire.rs:308

Dropping OutputStream, audio playing through this stream will stop
  2026-04-08T20:09:54.402577Z  INFO wayvr::subsystem::notifications: Notification listener stopped.
    at wayvr/src/subsystem/notifications.rs:142

  2026-04-08T20:09:54.610002Z ERROR wayvr: Fatal(the runtime failed to handle the function in an unexpected way that is not covered by another error result)
    at wayvr/src/main.rs:160

journalctl logs :

avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:29)
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:  Process kwin_wayland pid 2022 thread kwin_wayla:cs0 pid 2067
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x00008000012aa000 from client 0x1b (UTCL2)
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00600C30
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          Faulty UTCL2 client ID: CPG (0x6)
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          MORE_FAULTS: 0x0
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          WALKER_ERROR: 0x0
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          MAPPING_ERROR: 0x0
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          RW: 0x0
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:222 vmid:0 pasid:0)
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:   in page starting at address 0x0000000015a23000 from client 0x1b (UTCL2)
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x000009BC
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          Faulty UTCL2 client ID: CPF (0x4)
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          MORE_FAULTS: 0x0
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          WALKER_ERROR: 0x6
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          PERMISSION_FAULTS: 0xb
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          MAPPING_ERROR: 0x1
avril 08 22:06:42 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:          RW: 0x0
avril 08 22:06:44 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=533668, emitted seq=533672
avril 08 22:06:44 NZXT kernel: amdgpu 0000:09:00.0: amdgpu:  Process ROTTR.exe pid 25496 thread dxvk-submit pid 25856
avril 08 22:06:44 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: Starting gfx_0.0.0 ring reset
avril 08 22:06:44 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: Ring gfx_0.0.0 reset failed
avril 08 22:06:45 NZXT kernel: amdgpu 0000:09:00.0: amdgpu: [drm] *ERROR* Failed to initialize parser -125!

maledict · April 8, 2026, 8:39pm

DrKondi says that the report isn’t usable even if I’ve downloaded the debugging symbols multiple times already

maledict · April 8, 2026, 8:41pm

I think I maybe have the same issue as this one. It also shows a similar issue with the AMDGPU driver.

Franken14679 · April 9, 2026, 6:00pm

@maledict:

On this machine:

 > kinfo
Operating System: openSUSE Tumbleweed 20260408
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.11.0
Kernel Version: 6.19.11-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 8600G w/ Radeon 760M Graphics
Memory: 34 GB of RAM (32.8 GB usable)
Graphics Processor: AMD Radeon 760M Graphics
 >

Kontact was regularly crashing with a Segmentation Fault when quitting the application – until the newest Qt version hit the streets a week or so ago.

There was also a similar issue with Spectacle which was fixed with the KDE Plasma Version 6.6. There KDE Bug Reports dealing with these issues.
Spectacle: <https://bugs.kde.org/show_bug.cgi?id=517064>
Kontact: sorry, I can’t quickly find the relevant Bug Report.