Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: This had occurred a few times, recently. Before I reported this, it occurred nearly 40 times in two minutes, after I returned to my computer, with my user account de-authenticated, alongside reproductions of: - https://bugzilla.redhat.com/show_bug.cgi?id=2445811#c12 - https://bugzilla.redhat.com/show_bug.cgi?id=2480033#c0 - https://bugzilla.redhat.com/show_bug.cgi?id=2484616#c12 - https://bugzilla.redhat.com/show_bug.cgi?id=2483632#c0 After reporting this, it has occurred 1 247 times, in 10 minutes. https://discuss.kde.org/t/drkonqi-crashing-on-plasma-6-wayland/48086/2?u=rokejulianlockhart corroborates this. Version-Release number of selected component: plasma-drkonqi-6.7.0-1.fc44 Additional info: reporter: libreport-2.17.15 type: CCpp reason: drkonqi-coredump-launcher killed by SIGABRT journald_cursor: s=2c1910e140e64b2c86a6ef7504aaa761;i=22ff8a;b=61b93e4c89ad42aba42d54dd9ed9e511;m=91a90d21c;t=654b6befb5c39;x=ed4616b217efc93 executable: /usr/libexec/drkonqi-coredump-launcher cmdline: /usr/libexec/drkonqi-coredump-launcher cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 7.0.12-201.fc44.x86_64 backtrace_rating: 4 crash_function: qAbort package: plasma-drkonqi-6.7.0-1.fc44 Truncated backtrace: Thread no. 1 (10 frames) #4 qAbort at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/global/qassert.cpp:47 #5 qt_maybe_message_fatal<QString&> at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/global/qlogging.cpp:2170 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/global/qlogging.cpp:413 #7 QMessageLogger::fatal at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/global/qlogging.cpp:902 #8 init_platform at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/gui/kernel/qguiapplication.cpp:1368 #9 QGuiApplicationPrivate::createPlatformIntegration at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/gui/kernel/qguiapplication.cpp:1616 #10 QGuiApplicationPrivate::createEventDispatcher at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/gui/kernel/qguiapplication.cpp:1634 #11 QCoreApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:870 #12 QGuiApplicationPrivate::init at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/gui/kernel/qguiapplication.cpp:1667 #13 QGuiApplication::QGuiApplication at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/gui/kernel/qguiapplication.h:175
Created attachment 2146099 [details] File: proc_pid_status
Created attachment 2146100 [details] File: maps
Created attachment 2146101 [details] File: limits
Created attachment 2146102 [details] File: environ
Created attachment 2146103 [details] File: open_fds
Created attachment 2146104 [details] File: mountinfo
Created attachment 2146105 [details] File: os_info
Created attachment 2146106 [details] File: backtrace
https://bugzilla.redhat.com/show_bug.cgi?id=2441240#c15 has, since, also occurred.
I tried to connect to an external HDMI monitor (detected but not displayed), then I clicked log out and re-login, then the crash captured. reporter: libreport-2.17.15 type: CCpp reason: drkonqi-coredump-launcher killed by SIGABRT journald_cursor: s=ddccf3321454447ebb1b7990e286d6b8;i=3a14d;b=734518d1e5b44527b2e95bf396b2a2e0;m=11f16ff424;t=6550c3173f18c;x=10a857e7d0ecd267 executable: /usr/libexec/drkonqi-coredump-launcher cmdline: /usr/libexec/drkonqi-coredump-launcher cgroup: 0::/user.slice/user-1000.slice/user/app.slice/drkonqi-coredump-launcher rootdir: / uid: 1000 kernel: 7.0.12-201.fc44.x86_64 backtrace_rating: 4 crash_function: qAbort package: plasma-drkonqi-6.7.0-1.fc44
I used to get huge numbers of these on Fedora 44 up to KDE 6.7.0: Fri 2026-06-26 22:50:07 EDT 85807 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - Fri 2026-06-26 22:50:07 EDT 85821 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - Fri 2026-06-26 22:50:08 EDT 85834 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - Fri 2026-06-26 22:50:08 EDT 85847 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - Fri 2026-06-26 22:50:09 EDT 85860 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - Fri 2026-06-26 22:50:09 EDT 85873 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - Fri 2026-06-26 22:50:10 EDT 85886 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - Fri 2026-06-26 22:50:10 EDT 85900 1000 1000 SIGABRT none /usr/libexec/drkonqi-coredump-launcher - So these were the most recent ones on "coredumpctl list" for June 26, 2026 and on this day I had 190 of these. Then I upgraded to KDE 6.7.1-1 and rebooted. Since that reboot I've logged back in and don't see any new SIGABRTs. I suspect that KDE 6.7.1-1 Bugfix has fix this.
I agree. Shall close as `CurrentRelease`. If anyone knows of the upstream KDE GitLab MRs or Bugzilla bugs, please cite them.