Summary: | Plasmashell crashed when on moving icon on desktop. | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | yuvrajtalukdar |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | adamdavidsher, ascaris, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.18.5 | ||
Target Milestone: | 1.0 | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
yuvrajtalukdar
2020-05-11 17:05:28 UTC
Created attachment 128382 [details]
New crash information added by DrKonqi
plasmashell (5.18.5) using Qt 5.14.2
- What I was doing when the application crashed:
I'd noticed that the bottom row of icons was moved up one row, so I attempted to move them back down. The first time it caused Plasma to restart, and the second it just crashed with a DrKonqi dialog.
These are the first and second times it has happened. I don't know that it will, but l selected "sometimes" since it happened more than once just now.
-- Backtrace (Reduced):
#4 0x00007f4b61a475f5 in QVector<QQuickItemPrivate::ChangeListener>::indexOf (this=this@entry=0x55c34445d088, t=..., from=from@entry=0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:1010
#5 0x00007f4b61a3f49e in QVector<QQuickItemPrivate::ChangeListener>::removeOne (t=..., this=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:182
#6 QQuickItemPrivate::removeItemChangeListener (this=this@entry=0x55c34445d010, listener=listener@entry=0x55c34b62d200, types=..., types@entry=...) at items/qquickitem.cpp:3955
#7 0x00007f4b61b74ada in QQuickShaderEffectSource::~QQuickShaderEffectSource (this=0x55c34b62d1e0, __in_chrg=<optimized out>) at items/qquickshadereffectsource.cpp:213
#8 0x00007f4b61b74b39 in QQuickShaderEffectSource::~QQuickShaderEffectSource (this=0x55c34b62d1e0, __in_chrg=<optimized out>) at items/qquickshadereffectsource.cpp:218
*** This bug has been marked as a duplicate of bug 421170 *** |