Application: akonadi_sendlater_agent (5.19.3 (21.12.3)) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I tried opening Audacity while sharing my screen in a Skype call in Firefox Developer Edition 122.0b9, with the intent to show my father via Skype how he can record audio in Audacity. - Unusual behavior I noticed: Suddenly both screens went black, after a few seconds showed some `^@^@^@^@^@^@^@^@` in the TTY and KDE started back up with tons of "KDE:s kraschhanterare" windows with different processes whose name begins with "akonadi_", with the details stating it crashed with signal "Aborted (6)". Some of them include: * akonadi_mailmerge_agent * akonadi_unifiedmailbox_agent * akonadi_akonotes_resource * akonadi_maildir_resource * akonadi_archivemail_agent * [etc] Interestingly, KDE didn't crash again when opening and using Audacity in the exact same situation again. Firefox does no longer have camera access since the crash, but I haven't rebooted yet so that may fix the camera access. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: akonadi_sendlater_agent (akonadi_sendlater_agent), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140025438897152) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140025438897152) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140025438897152, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x00007f5a4c442476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f5a4c4287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x00007f5a4cc90ba3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f5a41707e45 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x00007f5a4171811a in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x00007f5a4cef17c8 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007f5a4cef4cb3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007f5a4cef54e3 in QSocketNotifier::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007f5a4db6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x00007f5a4ceb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f5a4cf13cc5 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007f5a4a651d3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007f5a4a6a7258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007f5a4a64f3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007f5a4cf130b8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007f5a4ceb875b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007f5a4cec0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x000055558b817ff4 in () #25 0x00007f5a4c429d90 in __libc_start_call_main (main=main@entry=0x55558b816630, argc=argc@entry=3, argv=argv@entry=0x7fffe05acdc8) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x00007f5a4c429e40 in __libc_start_main_impl (main=0x55558b816630, argc=3, argv=0x7fffe05acdc8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffe05acdb8) at ../csu/libc-start.c:392 #27 0x000055558b816665 in () [Inferior 1 (process 3601) detached] Possible duplicates by query: bug 474747, bug 473194, bug 472861, bug 472535, bug 471164. Rapportera till https://bugs.kde.org/
This means kwin_wayland has crashed. Please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports to get a backtrace for kwin_wayland and paste it here. Thanks!
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!
Created attachment 165728 [details] The crash handler windows in the window spread view. Well, I cannot get the stack trace as it seems to be a completely random crash, although I recently accidentally reproduced it on KDE 5.27 (from the Ubuntu jammy Backports repo). I tried to repeat it but it didn't crash again. I dragged a .desktop file for PyCharm (I don't have the snap but the .tar.gz) onto the panel, it didn't appear in there. So I dragged it onto there two more times without it appearing. Then I launched PyCharm from the .desktop file in `nemo` and as soon as it appeared in the panel I right-clicked onto the icon to pin it, right when the window tried closing itself (because the first window only is a splash screen). The context menu started appearing, then the whole desktop locked up and restarted to the same flood of crash handler windows. See the newly-attached screenshots.
The only stack trace I got was the one attached in the initial comment under the [KCrash handler] section.
I'm afraid we still need a kwin_wayland backtrace for this to be actionable. You may be able to use `coredumpctl` to get it; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
As I have so far been unable to determine a reliable way to trigger the bug I'll mark this as "RESOLVED→WORKSFORME" now… I have seen a similar, reliably triggerable crash, but it manifests a little differently and doesn't seem to be related AFAIK.