Bug 381035

Summary: Plasmashell crashing when changing the location of the panel
Product: [Plasma] plasmashell Reporter: Morbid <raist356>
Component: PanelAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version First Reported In: 5.10.0   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Morbid 2017-06-09 21:21:15 UTC 
On fully updated Manjaro - plasma 5.10.0 so far, laptop with external monitor connected, when changing the location of the panel to other screen border plasma shell crashes.
Output from the console, when I run it there after the crash and it crashed again when trying to do that again:
networkmanager-qt: virtual void NetworkManager::DevicePrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "Real"
ktp-common-internals: Current presence changed
ktp-common-internals: Current presence changed
QQmlComponent: Component is not ready
WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop"
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Base/ButtonStyle.qml:153:31: QML Item: Binding loop detected for property "implicitWidth"
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Base/ButtonStyle.qml:153:31: QML Item: Binding loop detected for property "implicitWidth"
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Base/ButtonStyle.qml:153:31: QML Item: Binding loop detected for property "implicitWidth"
[1]    4264 segmentation fault (core dumped)  plasmashell
Comment 1 Morbid 2017-06-10 15:48:50 UTC 
It still happens on 5.10.1
Comment 2 Christoph Feck 2017-06-21 15:15:35 UTC 
If this is still reproducible, please add the backtrace for the crash. For more information, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 3 Christoph Feck 2017-07-09 11:42:49 UTC 
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 Christoph Feck 2017-07-26 17:23:18 UTC 
No response, changing status.