https://bugs.kde.org/show_bug.cgi?id=521653
--- Comment #5 from alex zhang <[email protected]> --- I hit the crash again on the previous boot and collected a full gdb backtrace with debuginfod-enabled debug symbols. Crash summary: - Process: kwin_wayland - Signal: SIGSEGV - Time: 2026-07-05 08:02:46 CST - Boot ID: 5a5f796f2c6143928c37c2459b992b18 - Package: kwin-6.7.1-2.fc44.x86_64 - KWin version: 6.7.1 - KDE Frameworks: 6.27.0 - Qt: 6.11.1 - DrKonqi Sentry event ID: 92e91eb8ef904396b2ecec6e85b3fb54 System: - Fedora Linux 44 KDE Plasma Desktop Edition - Kernel: 7.0.14-201.fc44.x86_64 - Session: Plasma Wayland - GPU: AMD Navi 32 / Radeon RX 7700 XT / 7800 XT [1002:747e] - Driver: amdgpu - Mesa: 26.1.3-1.fc44 - libdrm: 2.4.134-1.fc44 - amd-gpu-firmware: 20260622-1.fc44 The crash happened right after login/session startup. Relevant journal lines just before the crash: ``` 2026-07-05 08:02:43 kernel: amdgpu 0000:0a:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:148 2026-07-05 08:02:45 systemd[2349]: Started plasma-kwin_wayland.service - KDE Wayland Compositor. 2026-07-05 08:02:45 kwin_wayland[2560]: No backend specified, automatically choosing drm 2026-07-05 08:02:46 kwin_wayland[2560]: Failed to load cursor theme "Layan-white-cursors" 2026-07-05 08:02:46 kwin_wayland[2560]: atomic commit failed: Device or resource busy 2026-07-05 08:02:46 kwin_wayland[2560]: atomic commit failed: Device or resource busy 2026-07-05 08:02:46 kwin_wayland[2560]: atomic commit failed: Device or resource busy 2026-07-05 08:02:46 kwin_wayland[2560]: atomic commit failed: Device or resource busy 2026-07-05 08:02:46 kwin_wayland[2560]: atomic commit failed: Device or resource busy 2026-07-05 08:02:46 kwin_wayland_wrapper[2560]: KCrash: Application 'kwin_wayland' crashing... crashRecursionCounter = 2 2026-07-05 08:02:46 systemd-coredump[2625]: Process 2560 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing... 2026-07-05 08:02:47 systemd-coredump[2626]: Process 2560 (kwin_wayland) of user 1000 dumped core. 2026-07-05 08:02:47 kernel: amdgpu 0000:0a:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:148 ``` The full backtrace points at: ``` Thread 1 (Thread 0x7f14afc86480 (LWP 2560)): #0 __pthread_kill_implementation (...) at pthread_kill.c:44 #1 __pthread_kill_internal (...) at pthread_kill.c:89 #2 __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 KCrash::defaultCrashHandler (sig=11) at /usr/src/debug/kf6-kcrash-6.27.0-1.fc44.x86_64/src/kcrash.cpp:630 #4 <signal handler called> #5 std::vector<std::unique_ptr<KWin::DrmCommit>>::size(...) at /usr/include/c++/16/bits/stl_vector.h:1109 #6 std::__detail::__erase_if<...> at /usr/include/c++/16/bits/erase_if.h:55 #7 std::erase_if<...> at /usr/include/c++/16/vector:118 #8 KWin::DrmGpu::pageFlipHandler(fd=31, sequence=509, sec=22, usec=466207, crtc_id=363, user_data=0x7f1434001370) at /usr/src/debug/kwin-6.7.1-2.fc44.x86_64/src/backends/drm/drm_gpu.cpp:559 #9 drmHandleEvent(fd=31, evctx=0x7ffd858536b0) at ../xf86drmMode.c:1070 #10 KWin::DrmGpu::dispatchEvents(...) at /usr/src/debug/kwin-6.7.1-2.fc44.x86_64/src/backends/drm/drm_gpu.cpp:594 ``` I am attaching: - `kwin_wayland-2560-gdb-bt-full.txt` - full gdb `thread apply all bt full` output with debuginfod enabled - `kwin_wayland-2560-relevant-journal.txt` - journal lines around the crash - `system-summary.txt` - package, kernel, session, and GPU summary The full gdb run emitted these warnings, but still completed and produced the backtrace: ``` warning: Can't open file /memfd:JSGCHeap:QtQml (deleted) during file-backed mapping note processing warning: Can't open file /memfd:JSVMStack:QtQml (deleted) during file-backed mapping note processing warning: .gdb_index address table has a range (0x6e02a0 - 0x6e02a1) that overlaps with an earlier range, ignoring .gdb_index ``` -- You are receiving this mail because: You are watching all bug changes.
