Application: plasmashell (5.27.80) Qt Version: 6.6.0 Frameworks Version: 5.240.0 Operating System: Linux 6.2.0-26-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.27.80 [CoredumpBackend] -- Information about the crash: My smarfon is connected with PC via KDE Connect. When I turn on WiFi in smartfon then Plasma shows notifications (i.e. not received call) and just after that crashes. Here is added full (three asterix) backtrace The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 doActivate<false>(QObject*, int, void**) (sender=0x562ac6602f30, signal_index=45, argv=0x0) at ./src/corelib/tools/qscopedpointer.h:110 [...] #8 0x00007f64e4f84f16 in QQmlDMAbstractItemModelData::metaCall(QMetaObject::Call, int, void**) (this=0x562ac6602f30, call=<optimized out>, id=<optimized out>, arguments=0x7ffcf1b685b0) at ./src/qmlmodels/qqmldmabstractitemmodeldata.cpp:46 #9 0x00007f64e7a6d51b in QQmlPropertyData::doMetacall<(QMetaObject::Call)2>(QObject*, int, void**) const (this=<optimized out>, argv=0x7ffcf1b685b0, idx=<optimized out>, object=<optimized out>) at ./obj-x86_64-linux-gnu/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:320 #10 QQmlPropertyData::writeProperty(QObject*, void*, QFlags<QQmlPropertyData::WriteFlag>) const (this=<optimized out>, target=<optimized out>, value=<optimized out>, flags=...) at ./obj-x86_64-linux-gnu/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:340 #11 0x00007f64e7b28813 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlRefPointer<QQmlContextData> const&, QFlags<QQmlPropertyData::WriteFlag>) (object=0x562ac6602f30, property=..., value=..., context=..., flags=...) at ./src/qml/qml/qqmlproperty.cpp:1536 Reported using DrKonqi
Created attachment 160994 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
No need to keep reporting these; Bug 472964 is tracking it already. *** This bug has been marked as a duplicate of bug 472964 ***