Application: plasmashell (5.27.6) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.3.9-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.6 [CoredumpBackend] -- Information about the crash: Notification about an incoming mail (-> Thunderbird) popped up. When closing the notification (by using the crosshair button), Plasma crashed. Automatic restart went OK. Happens occasionally, cannot be systematically reproduced /w every notification. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x00007f978a693dad in QtQml::qmlExecuteDeferred(QObject*) () from /lib64/libQt5Qml.so.5 #6 0x00007f978ab78e99 in QQuickTransition::prepare(QList<QQuickStateAction>&, QList<QQmlProperty>&, QQuickTransitionManager*, QObject*) () from /lib64/libQt5Quick.so.5 #7 0x00007f978ab6e3b7 in QQuickTransitionManager::transition(QList<QQuickStateAction> const&, QQuickTransition*, QObject*) () from /lib64/libQt5Quick.so.5 #8 0x00007f9788f191bb in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #9 0x00007f9789da519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 The reporter indicates this bug may be a duplicate of or related to bug 461072, bug 462715, bug 465706, bug 473055. Reported using DrKonqi
Created attachment 161104 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
No KDE code in the backtrace: Thread 1 (Thread 0x7f9786cc6980 (LWP 1792)): [KCrash Handler] #5 0x00007f978a693dad in QtQml::qmlExecuteDeferred(QObject*) () from /lib64/libQt5Qml.so.5 #6 0x00007f978ab78e99 in QQuickTransition::prepare(QList<QQuickStateAction>&, QList<QQmlProperty>&, QQuickTransitionManager*, QObject*) () from /lib64/libQt5Quick.so.5 #7 0x00007f978ab6e3b7 in QQuickTransitionManager::transition(QList<QQuickStateAction> const&, QQuickTransition*, QObject*) () from /lib64/libQt5Quick.so.5 #8 0x00007f9788f191bb in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #9 0x00007f9789da519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #10 0x00007f9788eed4f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #11 0x00007f9788f45889 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #12 0x00007f9788f4616c in ?? () from /lib64/libQt5Core.so.5 #13 0x00007f9787ae08d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #14 0x00007f9787ae0ce8 in ?? () from /lib64/libglib-2.0.so.0 #15 0x00007f9787ae0d7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #16 0x00007f9788f46496 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #17 0x00007f9788eebf8b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #18 0x00007f9788ef4420 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #19 0x000056526dc07a91 in ?? () #20 0x00007f978862abb0 in __libc_start_call_main () from /lib64/libc.so.6 #21 0x00007f978862ac79 in __libc_start_main_impl () from /lib64/libc.so.6 #22 0x000056526dc07e25 in ?? ()
(In reply to Nate Graham from comment #2) > No KDE code in the backtrace: > > Thread 1 (Thread 0x7f9786cc6980 (LWP 1792)): > ... > #22 0x000056526dc07e25 in ?? () Sorry to hear that the backtrace does not contain valid information. After opening the bug report, KDE's error data sending facility window remained open for > 3h; I considered this sufficient and closed the window, but maybe the tool was in fact still sending? Can I provide trace, coredump etc. data manually in case the crash happens again?
Nah you didn't anything wrong. It's just that the backtrace indicates that the problem is deep in Qt. So it will take someone with very deep knowledge of both Plasma and Qt's codebases to pinpoint whether this crash is caused by a Qt bug, or we're doing something in our implementation. Unfortunately that person is not me. :)
...On the other hand, I can do simple pattern recognition! *** This bug has been marked as a duplicate of bug 468180 ***