Bug 388681 - Plasma crashes after right-click on the Kicker's element (an app shortcut for example)
Summary: Plasma crashes after right-click on the Kicker's element (an app shortcut for...
Status: RESOLVED DUPLICATE of bug 383828
Alias: None
Product: plasmashell
Classification: Plasma
Component: Application Menu (Kicker) (show other bugs)
Version: master
Platform: ROSA RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-08 14:28 UTC by Andrew Novikov
Modified: 2018-02-09 11:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
error description (16.29 KB, text/plain)
2018-01-08 14:28 UTC, Andrew Novikov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Novikov 2018-01-08 14:28:50 UTC
Created attachment 109735 [details]
error description

right-click on the Kicker's element causes Plasma crash. Plasma recovers in a second automatically
Comment 1 Kai Uwe Broulik 2018-01-08 15:42:36 UTC
Pasting inline

Thread 1 (Thread 0x7ff6f31967c0 (LWP 6203)):
[KCrash Handler]
#5  0x00007ff6ec8ffaf7 in raise () at /lib64/libc.so.6
#6  0x00007ff6ec901738 in abort () at /lib64/libc.so.6
#7  0x00007ff6ed028d5e in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007ff6ef93edc0 in KPluginInfo::libraryPath() const () at /usr/lib64/libKF5Service.so.5
#9  0x00007ff6387d6512 in  () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so
#10 0x00007ff6387c95ee in  () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so
#11 0x00007ff6387cdf77 in  () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so
#12 0x00007ff6387d2132 in  () at /usr/lib64/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so
#13 0x00007ff6f00c0c24 in  () at /usr/lib64/libQt5Qml.so.5
#14 0x00007ff6f022945b in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, bool) () at /usr/lib64/libQt5Qml.so.5
#15 0x00007ff6f022a5d1 in QV4::QObjectWrapper::getQmlProperty(QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) const () at /usr/lib64/libQt5Qml.so.5
#16 0x00007ff6f0240e8a in QV4::Runtime::getProperty(QV4::ExecutionEngine*, QV4::Value const&, int) () at /usr/lib64/libQt5Qml.so.5
#17 0x00007ff6290aa133 in  ()
#18 0x00007ff6f0604b00 in QV4::CallContext::static_vtbl () at /usr/lib64/libQt5Qml.so.5
#19 0x00007ff6d15a93f8 in  ()
#20 0x000000000262abd0 in  ()
#21 0x00007ffe5404e590 in  ()
#22 0x0000000007b43f30 in  ()
#23 0x0000000000000002 in  ()
#24 0x00007ff6d15a94b0 in  ()
#25 0x00007ff6d15a9410 in  ()
#26 0x00007ff6d15a9500 in  ()
#27 0x00007ff6f01e116f in  () at /usr/lib64/libQt5Qml.so.5
#28 0x00007ff6f02cae7b in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib64/libQt5Qml.so.5
#29 0x00007ff6f0275534 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib64/libQt5Qml.so.5
#30 0x00007ff6f0275aa3 in  () at /usr/lib64/libQt5Qml.so.5
#31 0x00007ff6f02aafb4 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib64/libQt5Qml.so.5
#32 0x00007ff6f0258ca4 in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) () at /usr/lib64/libQt5Qml.so.5
#33 0x00007ff6ed1f70f2 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#34 0x00007ff6f0255699 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Qml.so.5
#35 0x00007ff6f02a24ec in  () at /usr/lib64/libQt5Qml.so.5
#36 0x00007ff6f022bf9c in  () at /usr/lib64/libQt5Qml.so.5
#37 0x00007ff6f022d258 in  () at /usr/lib64/libQt5Qml.so.5
#38 0x00007ff6f022dbdf in QV4::QObjectMethod::callInternal(QV4::CallData*) const () at /usr/lib64/libQt5Qml.so.5
#39 0x00007ff6f0243419 in QV4::Runtime::callActivationProperty(QV4::ExecutionEngine*, int, QV4::CallData*) () at /usr/lib64/libQt5Qml.so.5
Comment 2 Eike Hein 2018-01-09 02:44:26 UTC
Could you install debug symbols for plasma-desktop and produce another backtrace? Your crash looks interesting, but the backtrace has too many missing symbols to make sense of it.
Comment 3 Christoph Feck 2018-01-22 23:18:46 UTC
If this is reproducible, please add a backtrace with debug symbols. For help, please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 4 David Edmundson 2018-02-09 11:21:44 UTC

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