Plasmashell crashed unexpectedly when I clicked on the system tray, the "Networks" icon. Reproducible: Couldn't Reproduce Steps to Reproduce: I can't reliably reproduce the crash. It happened once. I had other plasmashell crashes under different circumstances, so it's probable that clicking on the "Network" icon is not the cause of the crash. Kubuntu 15.04, x86_64, KDE Framework 5.3 installed from Kubuntu backports. Nvidia drivers 346.59.
Created attachment 92496 [details] Crash stack backtrace
[KCrash Handler] #6 testAndSetRelaxed<QMutexData*> (currentValue=<synthetic pointer>, newValue=0x1, expectedValue=0x0, _q_value=@0x7fd764266190: 0x0) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259 #7 testAndSetAcquire<QMutexData*, QMutexData*> (currentValue=<synthetic pointer>, newValue=0x1, expectedValue=0x0, _q_value=@0x7fd764266190: 0x0) at ../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:166 #8 testAndSetAcquire (currentValue=<synthetic pointer>, newValue=0x1, expectedValue=0x0, this=0x7fd764266190) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:270 #9 fastTryLock (current=<synthetic pointer>, this=0x7fd764266190) at thread/qmutex.h:82 #10 QMutex::lock (this=0x7fd764266190) at thread/qmutex.cpp:212 #11 0x00007fd765c4080b in QQmlEnginePrivate::typeCategory(int) const () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x00007fd765c96b36 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x00007fd765c96e4b in QQmlPropertyCache::resolve(QQmlPropertyData*) const () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x00007fd765c96e74 in QQmlPropertyCache::ensureResolved(QQmlPropertyData*) const () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x00007fd765c97194 in QQmlPropertyCache::findProperty(QStringHash<QPair<int, QQmlPropertyData*> >::ConstIterator, QQmlVMEMetaObject const*, QQmlContextData*) const () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 Pasting relevant bit inline
*** Bug 345898 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 343687 ***