Application: plasmashell (6.1.80) (Compiled from sources) ApplicationNotResponding [ANR]: false Qt Version: 6.9.0 Frameworks Version: 6.5.0 Operating System: Linux 6.10.2-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.80 [CoredumpBackend] -- Information about the crash: Steps to reproduce: 1. Make the enable wifi (or enable airplane mode) tooltip stuck like described here: https://bugs.kde.org/show_bug.cgi?id=488912 2. Once the tooltip is stuck/persistent open the plasma-nm tray icon again. 3. Plasma shell is crashing Note: Can reproduce the stuck/persistend tooltip on plasma 6.1.3 compiled against qt6 6.7.2.1 BUT NOT the crash. The crash can be reproduced every time. -- Backtrace (Reduced): #5 0x0000724fc803819f in QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::get (this=<optimized out>) at /home/duha/kde/src/qtbase/src/corelib/tools/qscopedpointer.h:112 [...] #8 QWindow::mapToGlobal (this=0x0, pos=...) at /home/duha/kde/src/qtbase/src/gui/kernel/qwindow.cpp:2917 #9 0x0000724fc9605f5d in QQuickItem::mapToItem (this=this@entry=0x637f4c9a9c20, item=0x637f4abd94d0, point=...) at /home/duha/kde/src/qtdeclarative/src/quick/items/qquickitem.cpp:8778 #10 0x0000724fc1937a69 in QQuickPopupPositioner::reposition (this=0x637f4cafb7a0) at /home/duha/kde/src/qtdeclarative/src/quicktemplates/qquickpopuppositioner.cpp:153 #11 0x0000724fc960dca5 in operator() (listener=..., __closure=<optimized out>) at /home/duha/kde/src/qtdeclarative/src/quick/items/qquickitem.cpp:3906 Reported using DrKonqi
Created attachment 172156 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
I don't see KDE code in the backtrace, and I notice you're using a compiled-from-source unreleased Qt version. It would appear that the issue described in Bug 475646 now causes a crash due to changes in Qt. In a general sense, this crash should be reported to Qt. However in this specific case we know our code is at fault for causing Bug 475646, so maybe we should just fix that.
Bug 475646 has been fixed now, and with the fix applied, I can't reproduce the crash described here in the steps to reproduce.