https://bugs.kde.org/show_bug.cgi?id=508534
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #6 from [email protected] --- Dear KDE team, I hope this message finds you well. I am encountering a recurring segmentation fault (SIGSEGV) with the kwin_wayland process on my system running Nobara 42. I’m a beginner with debugging, so I apologize if the following information is not as detailed as it could be. I would appreciate any guidance you can provide. Here are the relevant details: System Information: OS: Nobara 42 (based on Fedora) KWin version: 6.4.4-2.fc42 (debug symbols loaded) Kernel: (add kernel version with uname -r) Error Signal: SIGSEGV (Segmentation Fault) Debugging Attempt: I’ve attempted to debug the core dump generated by the crash using GDB. Below are the results: Backtrace (Core dump generated by /usr/bin/kwin_wayland): Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fe81788209c in ?? () [Current thread is 1 (LWP 6519)] warning: failed to parse execution context from corefile: Cannot access memory at address 0x7ffce1ed8fe0 Failed to read a valid object file image from memory. The core dump shows a segmentation fault in the kwin_wayland process. There are warnings related to the inability to open several deleted memory files, such as: warning: Can't open file /memfd:kwin-dmabuf-feedback-table (deleted) during file-backed mapping note processing warning: Can't open file /memfd:wayland-shm (deleted) during file-backed mapping note processing ... warning: failed to parse execution context from corefile: Cannot access memory at address 0x7ffce1ed8fe0 Additional Information: I have tried loading debug symbols (kwin-debuginfo) for more detailed analysis, but there are still issues accessing memory in the core dump. A similar crash happens with systemsettings when trying to access kcm_kscreen: Core was generated by `/usr/bin/systemsettings kcm_kscreen`. The same type of warning and memory access issues are present. I also attempted to gather more information via drkonqi using the following commands, but it wasn’t able to parse the context: Starting debugger gdb --init-eval-command=maint set dwarf max-cache-age 0 --init-eval-command=set auto-solib-add off --nw --nx --batch --command=/tmp/drkonqi.obpaim --command=/tmp/drkonqi.iNVJer --core=/tmp/drkonqi-core.gnhkdH/core /usr/bin/systemsettings ... No solib and no image found for frame #0 on thread. Apologies and Further Information: As a beginner, I’m still learning how to provide effective debug information. I hope this data is useful, but please let me know if anything else is required. I’d be more than happy to try again with more guidance. Thank you for your time and help in resolving this issue. I really appreciate the work you do! Best regards, -- You are receiving this mail because: You are watching all bug changes.
