`plasmashell` segfaulting after upgrade to `40.20240714.0`

Stack traces in drkonqi contain the following:
Thread 1 (Thread 0x7f281e0006c0 (LWP 7834)):
[KCrash Handler]
#4 0x00007f285fa0fccf in QQmlPropertyCacheCreator<QQmlTypeCompiler>::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlError*) const () from /lib64/libQt6Qml.so.6
Thread 1 (Thread 0x7f281e0006c0 (LWP 7834)):
[KCrash Handler]
#4 0x00007f285fa0fccf in QQmlPropertyCacheCreator<QQmlTypeCompiler>::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlError*) const () from /lib64/libQt6Qml.so.6
Solution:
Likely you've run into this bug (https://bugs.kde.org/show_bug.cgi?id=418148) which is itself a QT bug( https://bugreports.qt.io/browse/QTBUG-62302). Resolved this by wiping all qmlcaches from my home directory: ```...
Jump to solution
1 Reply
Solution
Krin
Krin6mo ago
Likely you've run into this bug (https://bugs.kde.org/show_bug.cgi?id=418148) which is itself a QT bug( https://bugreports.qt.io/browse/QTBUG-62302). Resolved this by wiping all qmlcaches from my home directory:
cd ~/.cache && find . -type d -name '*qmlcache*' -exec rm -rf {} \;
cd ~/.cache && find . -type d -name '*qmlcache*' -exec rm -rf {} \;
Want results from more Discord servers?
Add your server