Application: plasmashell (6.3.5) ApplicationNotResponding [ANR]: false Qt Version: 6.9.0 Frameworks Version: 6.13.0 Operating System: Linux 6.14.5-arch1-1 x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.3.5 [CoredumpBackend] -- Information about the crash: Plasma sometimes crashes and relaunches. It doesn't happen consistently, but some actions that trigger it include: - Putting the machine to sleep and waking it back up. - Switching monitor inputs to a different gpu and then switching back. I'm not sure if it is related but I've only noticed this trigger it when I launch my Windows 10 Virtual Machine, so I switch off the iGPU to my dedicated Nvidia one. When I come back to the host (Arch) I sometimes get the crash report or even 2 on some occasions. The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x000070c05c6da43c in QQmlData::wasDeleted (priv=0x6) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmldata_p.h:307 #6 QQmlData::wasDeleted (object=0x5ea892a24aa0) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/qml/qqmldata_p.h:322 #7 QV4::QObjectWrapper::wrap (engine=0x5ea89295f330, object=0x5ea892a24aa0) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper_p.h:245 #8 0x000070c05c7d8bab in QV4::loadProperty (v4=<optimized out>, wrapper=<optimized out>, object=<optimized out>, property=...) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:126 #9 0x000070c05c7da2ba in QV4::QObjectWrapper::getQmlProperty (engine=0x5ea89295f330, qmlContext=..., wrapper=0x70c02c2733c0, object=0x5ea89299ff00, name=0x70c0341be5c8, flags=..., hasProperty=0x0, property=0x0) at /usr/src/debug/qt6-declarative/qtdeclarative/src/qml/jsruntime/qv4qobjectwrapper.cpp:525 Reported using DrKonqi
Created attachment 181184 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Thank you for the bug report! This crash is already being tracked, marking as a duplicate. *** This bug has been marked as a duplicate of bug 500044 ***