Created attachment 178433 [details] the stack trace of the core dump file SUMMARY Related to issue: https://bugs.kde.org/show_bug.cgi?id=500165 I found out that if a crash happen while the graphical environment is not ready like kwin_wayland crashing, the Drkonqi will SIGABRT crash. STEPS TO REPRODUCE I don't know. OBSERVED RESULT Drkonqi crashed after other crash happened in non-graphics environment. EXPECTED RESULT Drkonqi do not crash. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.6.72-x64v3-xanmod1-1-lts (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION Related log I found in journald 2月 16 14:51:21 Bryan-YOGA14s drkonqi[2185]: Failed to create wl_display (连接被拒绝) 2月 16 14:51:21 Bryan-YOGA14s systemd[957]: Starting Portal service... 2月 16 14:51:21 Bryan-YOGA14s drkonqi[2185]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found. 2月 16 14:51:21 Bryan-YOGA14s drkonqi[2185]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: wayland-egl, wayland, eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, xcb. 2月 16 14:51:21 Bryan-YOGA14s systemd-coredump[2192]: Process 2185 (drkonqi) of user 963 terminated abnormally with signal 6/ABRT, processing... 2月 16 14:51:21 Bryan-YOGA14s systemd[1]: Started Process Core Dump (PID 2192/UID 0). 2月 16 14:51:21 Bryan-YOGA14s systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
> I found out that if a crash happen while the graphical environment is not ready like kwin_wayland crashing You'll have to explain how that happens in greater detail, please. Also a complete journal might help.
I'm using Arch Linux as my daily drive. I updated my system this morning and rebooted to a black screen. I got into TTY and found out that the /usr/bin/kwin_wayland crashed and Drkonqi crashed too. But the strange is that the SDDM was still running. And every time I tried to restart SDDM, the Drkonqi will crash after kwin_wayland crash. Here is the log from journald: https://0x0.st/8N6s.txt
A possibly relevant merge request was started @ https://invent.kde.org/plasma/drkonqi/-/merge_requests/312
Git commit 7dca985d21d76a98b4d39196404060c928afb9f4 by Harald Sitter. Committed on 21/03/2025 at 12:34. Pushed by sitter into branch 'master'. coredump: don't start units on system users (e.g. sddm) while this may eventually become useful we are currently not supporting it M +1 -0 src/coredump/launcher/drkonqi-coredump-launcher.socket M +1 -0 src/coredump/launcher/drkonqi-coredump-launcher@.service.cmake M +1 -0 src/coredump/processor/drkonqi-coredump-pickup.service.cmake https://invent.kde.org/plasma/drkonqi/-/commit/7dca985d21d76a98b4d39196404060c928afb9f4
Git commit 0bfb27891b9b9d11503a0a4e69a860a807cd5eb2 by Harald Sitter. Committed on 21/03/2025 at 12:48. Pushed by sitter into branch 'Plasma/6.3'. coredump: don't start units on system users (e.g. sddm) while this may eventually become useful we are currently not supporting it (cherry picked from commit 7dca985d21d76a98b4d39196404060c928afb9f4) Co-authored-by: Harald Sitter <sitter@kde.org> M +1 -0 src/coredump/launcher/drkonqi-coredump-launcher.socket M +1 -0 src/coredump/launcher/drkonqi-coredump-launcher@.service.cmake M +1 -0 src/coredump/processor/drkonqi-coredump-pickup.service.cmake https://invent.kde.org/plasma/drkonqi/-/commit/0bfb27891b9b9d11503a0a4e69a860a807cd5eb2