Created attachment 142943 [details] drkonqi crash report SUMMARY drkonqi crashes when attempt to click on developer information tab or report bug button after wayland related plasmashell crash. See bug 438839 for crash attempting to generate backtrace of to request reopening. STEPS TO REPRODUCE 1. Experience crash per bug 438839 and related duplicates. 2. Click on either "report bug" or the "Developer Information" tab in drkonqi OBSERVED RESULT Reporter freezes for extended period before crashing. EXPECTED RESULT Able to get backtrace either via the developer information tab or the report bug button. SOFTWARE/OS VERSIONS Operating System: Ubuntu 21.10 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-21-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION System is configured to receive updates from the Kubuntu updates and backports PPAs. Crash can be reproduced every time. BACKTRACE Application: The KDE Crash Handler (drkonqi), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140569437149632) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140569437149632) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140569437149632, signo=signo@entry=6) at pthread_kill.c:91 #7 0x00007fd8e2ac3476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007fd8e2aa97b7 in __GI_abort () at abort.c:79 #9 0x00007fd8e2f68ba3 in qt_message_fatal (message=<synthetic pointer>..., context=...) at global/qlogging.cpp:1914 #10 QMessageLogger::fatal (this=this@entry=0x7ffd9e6a3840, msg=msg@entry=0x7fd8e1aab078 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 #11 0x00007fd8e1a0fe45 in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at ./src/client/qwaylanddisplay.cpp:209 #12 QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at ./src/client/qwaylanddisplay.cpp:204 #13 0x00007fd8e1a2006a in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x56093b75f770) at ./src/client/qwaylanddisplay.cpp:222 #14 0x00007fd8e31c8a88 in doActivate<false> (sender=0x56093b7a3360, signal_index=4, argv=0x7ffd9e6a3940) at kernel/qobject.cpp:3898 #15 0x00007fd8e31c1d67 in QMetaObject::activate (sender=sender@entry=0x56093b7a3360, m=m@entry=0x7fd8e342d800 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #16 0x00007fd8e318dba7 in QAbstractEventDispatcher::awake (this=this@entry=0x56093b7a3360) at .moc/moc_qabstracteventdispatcher.cpp:149 #17 0x00007fd8e31ea5db in QEventDispatcherGlib::processEvents (this=0x56093b7a3360, flags=...) at kernel/qeventdispatcher_glib.cpp:430 #18 0x00007fd8e318fa9b in QEventLoop::exec (this=this@entry=0x7ffd9e6a3a60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #19 0x00007fd8e3198024 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #20 0x00007fd8e37e4d10 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #21 0x00007fd8e3ef8629 in QApplication::exec () at kernel/qapplication.cpp:2824 #22 0x000056093b005829 in main (argc=<optimized out>, argv=<optimized out>) at ./src/main.cpp:229 [Inferior 1 (process 29603) detached]
> "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893 This means that KWin crashed; when this happens, all apps automatically crash too. Can you get a backtrace of the kwin_wayland crash? You may be able to retrieve it with the `coredumpctl` utility. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Created attachment 143353 [details] kwin_wayland crash backtrace Here's what I believe to be the backtrace. I didn't have anything in the coredumpctl list, even with multiple repeats, so I had to follow the copy and paste instructions on how to attach GDB to kwin on wayland in the debugging community wiki page.
Hmm, not very helpful to my eyes, but maybe KWin developers can see something useful in it.
No, the backtrace looks incomplete. How can the crash be reproduced?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
(In reply to Vlad Zahorodnii from comment #4) > No, the backtrace looks incomplete. How can the crash be reproduced? Just turn the monitor off then back on when running on Wayland in the bug originally linked. After the resulting plasmashell crash and recovery, click on the developer information tab or report bug button. At this point drkonqi will hang before crashing.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!