When I get a crash, DrKonki crashes after showing GUI. STACKTRACE #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007539128a56d3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89 #2 0x000075391284bba0 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x0000753912833582 in __GI_abort () at abort.c:73 #4 0x0000753912e905c2 in qAbort () at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qassert.cpp:49 #5 qt_message_fatal<QString&> (context=..., message=...) at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:2130 #6 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x753913f816e3 "%s", ap=ap@entry=0x7ffe87bb6c78) at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:382 #7 0x0000753912e9154b in QMessageLogger::fatal (this=this@entry=0x7ffe87bb71b0, msg=msg@entry=0x753913f816e3 "%s") at /usr/src/debug/qt6-base/qtbase/src/corelib/global/qlogging.cpp:884 #8 0x00007539138def5d in init_platform (pluginNamesWithArguments=..., platformPluginPath=..., platformThemeName=..., argc=@0x7ffe87bb761c: 19, argv=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qguiapplication.cpp:1327 #9 QGuiApplicationPrivate::createPlatformIntegration (this=0x6477a47827c0) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qguiapplication.cpp:1580 #10 0x000075391398acd8 in QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qguiapplication.cpp:1599 #11 0x0000753912f58a7d in QCoreApplicationPrivate::init (this=this@entry=0x6477a47827c0) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qcoreapplication.cpp:931 #12 0x000075391398ad6e in QGuiApplicationPrivate::init (this=this@entry=0x6477a47827c0) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qguiapplication.cpp:1627 #13 0x00007539142f9ae6 in QApplicationPrivate::init (this=0x6477a47827c0) at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:474 #14 0x00007539142f9c42 in QApplication::QApplication (this=<optimized out>, argc=<optimized out>, argv=<optimized out>, this=<optimized out>, argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:462 #15 0x0000647798fd61ef in main (argc=<optimized out>, argv=0x7ffe87bb7a58) at /usr/src/debug/drkonqi/drkonqi-6.3.0/src/main.cpp:133 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-arch1-1 (64-bit) Graphics Platform: Wayland Graphics Processor 1: AMD Radeon RX Vega M GL Graphics Graphics Processor 2: Mesa Intel® HD Graphics 630
Please fill in the bug report template SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT
(In reply to Harald Sitter from comment #1) > Please fill in the bug report template SUMMARY When I get a crash, DrKonqi crashes after showing GUI. STEPS TO REPRODUCE 1. Get a crash OBSERVED RESULT DrKonqi crashes. EXPECTED RESULT DrKonqi shows GUI with further actions.
> STEPS TO REPRODUCE > 1. Get a crash A crash of what?
(In reply to Harald Sitter from comment #3) > > STEPS TO REPRODUCE > > 1. Get a crash > > A crash of what? Doesn't matter. Any kind of crash that is supposed to open drkonqi window. I had this issue while getting a crash of plasmashell, kwin, xdg-desktop-portal-kde. Sometimes DrKonqi itself crashed right away (this issue) and sometimes it doesn't crash but then it will crash later (BUG 500249)
So, say plasmashell crashes. What happens next? Do you get the crash notification? How do you become aware that drkonqi crashed? Does drkonqi start when drkonqi crashes? Does this happen with a new user? Please attach some journal output from when that happens
Created attachment 178480 [details] journald content (In reply to Harald Sitter from comment #5) > So, say plasmashell crashes. What happens next? Do you get the crash notification? Yes, and when I press "report bug". Then DrKonqi window briefly appears and then closes. >How do you become aware that drkonqi crashed? 1. Visually (it disappears) 2. Notification appears saying "DrKonqi crashed" 3. Record appears in coredumpctl list > Does drkonqi start when drkonqi crashes? Automatically no, but I am getting a notification. > Does this happen with a new user? I don't know, haven't tried that. > Please attach some journal output from when that happens In attachment, "thread 6304" is drkonqi.
Kwin crashes, means you have no wayland compositor, means Qt aborts because it can't start the wayland backend. All of this happens during a logout which makes it impossible to recover since everything is in the process of shutting down.
*** Bug 500251 has been marked as a duplicate of this bug. ***
(In reply to Harald Sitter from comment #7) > Kwin crashes, means you have no wayland compositor, means Qt aborts because it can't start the wayland backend. Even if it were true, shutdown must not fail with core dumps. > All of this happens during a logout which makes it impossible to recover since everything is in the process of shutting down. I am staring at the desktop while it's happening and I certainly did not turn system off so I am fairly sure it is not happening during logout.
Please attach a complete journal and a complete backtrace. https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Backtraces
I believe both this and BUG 500251 related to vulkan renderer because if I switch to OpenGL it all goes away. I use vulkan because of BUG 494505 which doesn't seem to be present in wayland though. So this is likely the bug inside platform integration and not something related to drkonqi. But I'll grab a proper stacktrace first.
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.