When adding a default panel plasmashell crashes. The new panel has been added when plasmashell is restarted. This only occurs for default panels - adding an empty panel works fine. Plasmashell returns this when it crashes: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item. [1]+ Segmentation fault (core dumped) plasmashell Tested in Fedora 25 with Plasma 5.8.3 & 5.8.1 Reproducible: Always Steps to reproduce: Right click on desktop > Add Panel > Default panel Graphics: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340]
needs a backtrace with debug symbols
Created attachment 102431 [details] plasmashell backtrace backtrace from 5.8.1 attached
Thanks for the update. (gdb) bt #0 QQmlVMEMetaObject::metaCall (this=0x55555b0ca050, o=<optimized out>, c=QMetaObject::ReadProperty, _id=4, a=0x7fffff7ff110) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlvmemetaobject.cpp:596 #1 0x00007ffff4f90641 in ReadAccessor::Indirect (property=..., n=0x0, output=0x7fffff7ff0f0, object=0x55555b084820) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4qobjectwrapper.cpp:125 #2 LoadProperty<ReadAccessor::Indirect> (v4=v4@entry=0x5555559265c0, object=object@entry=0x55555b084820, property=..., notifier=0x0) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4qobjectwrapper.cpp:160 #3 0x00007ffff4f90d72 in QV4::QObjectWrapper::getProperty (engine=engine@entry=0x5555559265c0, object=0x55555b084820, property=0x7fffc06a3de8, captureRequired=captureRequired@entry=true) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4qobjectwrapper.cpp:386 #4 0x00007ffff4f91702 in QV4::QObjectWrapper::getQmlProperty (this=0x7fffcb000700, qmlContext=qmlContext@entry=0x55555b085a20, name=name@entry=0x7fffcb0006c0, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7fffff7ff350, includeImports=includeImports@entry=false) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4qobjectwrapper.cpp:324 #5 0x00007ffff4f954dc in QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x5555559265c0, qmlContext=qmlContext@entry=0x55555b085a20, object=<optimized out>, name=name@entry=0x7fffcb0006c0, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7fffff7ff350) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4qobjectwrapper.cpp:411 #6 0x00007ffff503bee7 in QV4::QmlContextWrapper::get (m=<optimized out>, name=0x7fffcb0006c0, hasProperty=0x7fffff7ff430) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/qml/qqmlcontextwrapper.cpp:230 #7 0x00007ffff4f1a6c6 in QV4::Object::get (hasProperty=0x7fffff7ff430, name=0x7fffcb0006c0, this=<optimized out>) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4object_p.h:304 #8 QV4::ExecutionContext::getProperty (this=<optimized out>, name=0x7fffcb0006c0) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4context.cpp:469 #9 0x00007ffff4fa7c30 in QV4::Runtime::getActivationProperty (engine=0x5555559265c0, nameIndex=<optimized out>) at /usr/src/debug/qtdeclarative-opensource-src-5.7.0/src/qml/jsruntime/qv4runtime.cpp:724 #10 0x00007fff31f16099 in ?? () #11 0x0000000000000000 in ?? () (gdb)
same problem here with plasme 5.8.5 on KDE-Neon. Also the new panel is added on the wrong screen (i want a panel on my secondary screen - it appears on the primary one) It also crashes with default settings (after removing plasma-org.kde.plasma.desktop-appletsrc and plasmashellrc). last line of output (appears 5 times): file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Base/SliderStyle.qml:224:13: QML Loader: Binding loop detected for property "x" backtrace: Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x00007efcd4cd0637 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 (gdb) bt #0 0x00007efcd4cd0637 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #1 0x00007efcd4cd0716 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #2 0x00007efcd4cb0aa1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #3 0x00007efcd4cb17da in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x00007efcd4cb21ba in QV4::QObjectWrapper::getQmlProperty(QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) const () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x00007efcd4cb247f in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x00007efcd4d55567 in QV4::QmlContextWrapper::get(QV4::Managed const*, QV4::String*, bool*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x00007efcd4c3bc1e in QV4::ExecutionContext::getProperty(QV4::String*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x00007efcd4cc4170 in QV4::Runtime::getActivationProperty(QV4::ExecutionEngine*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x00007efc18055479 in ?? () #10 0x0000000000000078 in ?? () #11 0x458201c4ab9b5c00 in ?? () #12 0x0000000000000008 in ?? () #13 0x00000000010a84d0 in ?? () #14 0x00000000010a84d0 in ?? () #15 0x00007efcb959a698 in ?? () #16 0x0000000000000000 in ?? ()
valid on fedora plasma 5.8.6 valid on mageia plasma 5.8.5
it works in linux Mint 18.1. The difference is the Qt version 5.6.1 in Mint ( 5.6.2 in mageia )
I think this is a Qt bug, and reported downstream.
I can also confirm this bug. Application: plasmashell (5.8.7) Qt Version: 5.6.1 Frameworks Version: 5.35.0 Operating System: Linux 4.8.0-53-generic x86_64 Distribution: Linux Mint 18.2 Sonya
*** This bug has been marked as a duplicate of bug 383828 ***