Bug 416030

Summary: Plasma has started crashing frequently. I don't know the root cause, I haven't been able to work it out.
Product: [Plasma] plasmashell Reporter: Tim Richardson <tim>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde, nate, plasma-bugs
Priority: NOR Keywords: drkonqi
Version: 5.17.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 Tim Richardson 2020-01-08 23:52:18 UTC
Application: plasmashell (5.17.5)

Qt Version: 5.13.2
Frameworks Version: 5.65.0
Operating System: Linux 5.3.13-custom x86_64
Distribution: KDE neon User Edition 5.17

-- Information about the crash:
plasma crashes, I don't know why. It's happening every few hours, this problem started only in the past three days.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#6  0x00007ff187a79e61 in KIO::DropJob::setApplicationActions(QList<QAction*> const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5
#7  0x00007ff1720ff874 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so
#8  0x00007ff172100740 in  () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so
[...]
#10 0x00007ff182956237 in KIO::TransferJob::mimetype(KIO::Job*, QString const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#11 0x00007ff182956e12 in KIO::TransferJob::slotMimetype(QString const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5


Possible duplicates by query: bug 415994, bug 415991, bug 415960, bug 415956, bug 415955.

Reported using DrKonqi
Comment 1 Tim Richardson 2020-01-08 23:52:19 UTC
Created attachment 124985 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Kai Uwe Broulik 2020-01-09 08:10:11 UTC
Apepars you are dragging stuff onto the desktop?
Comment 3 Nate Graham 2021-02-26 17:54:40 UTC

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