Bug 381611 - Task Panel crashes with Segmentation fault after size/behaviour modification.
Summary: Task Panel crashes with Segmentation fault after size/behaviour modification.
Status: RESOLVED DUPLICATE of bug 366653
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.8.6
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-24 16:50 UTC by Psijic
Modified: 2017-06-26 13:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
psijic: X11?

Attachments
Log (16.69 KB, text/plain)
2017-06-24 16:50 UTC, Psijic 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Psijic 2017-06-24 16:50:37 UTC 
Created attachment 106276 [details]
Log

Task Panel crashes with Segmentation fault after size/behaviour modification.
OpenSuse Leap 42.2, Kernel 4.4.70
Comment 1 Marco Martin 2017-06-26 13:35:37 UTC 
pasting inline
Thread 1 (Thread 0x7fca870fb900 (LWP 2500)):
[KCrash Handler]
#6  0x00007fca83ed1a78 in ?? () from /usr/lib64/libQt5Qml.so.5
#7  0x00007fca83ed28e0 in QV4::ExecutionEngine::toVariant(QV4::Value const&, int, bool) () from /usr/lib64/libQt5Qml.so.5
#8  0x00007fca83f51170 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () from /usr/lib64/libQt5Qml.so.5
#9  0x00007fca83f5182f in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () from /usr/lib64/libQt5Qml.so.5
#10 0x00007fca83f5194d in QV4::QObjectWrapper::put(QV4::Managed*, QV4::String*, QV4::Value const&) () from /usr/lib64/libQt5Qml.so.5
#11 0x00007fca83f621f6 in QV4::Runtime::setProperty(QV4::ExecutionEngine*, QV4::Value const&, int, QV4::Value const&) () from /usr/lib64/libQt5Qml.so.5
#12 0x00007fc9c2416158 in ?? ()
#13 0x0000000a00000000 in ?? ()
#14 0x000000000000000a in ?? ()
#15 0x0000000000000000 in ?? ()
Comment 2 Marco Martin 2017-06-26 13:37:15 UTC 

*** This bug has been marked as a duplicate of bug 366653 ***