Bug 418569

Summary: Plasma crash upon copy image
Product: [Plasma] plasmashell Reporter: Xaekai <kdebugs>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: crash CC: plasma-bugs
Priority: NOR Keywords: drkonqi
Version: 5.17.5   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Xaekai 2020-03-07 04:47:49 UTC
Application: plasmashell (5.17.5)

Qt Version: 5.14.0
Frameworks Version: 5.66.0
Operating System: Linux 5.4.13-arch1-1 x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:

I was working in GIMP and copied the visible image (the command accessed by the default shortcut of CTRL SHIFT C) which crashed both GIMP and Plasma. This has happened twice within 20 minutes. I did recently close a desktop notes widget and saw a bug report mentioning that same circumstance but was unable to determine if this was related.

I only share this bug report because this is the first time I have ever seen the KDE crash reporter suggest the report may actually be useful in almost a decade of using KDE.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#6  0x0000000000000070 in  ()
[...]
#8  0x00007f74a9b2ae1d in QQuickShortcutContext::matcher(QObject*, Qt::ShortcutContext) () at /usr/lib/libQt5QuickTemplates2.so.5
#9  0x00007f74affa84c4 in QShortcutMap::find(QKeyEvent*, int) () at /usr/lib/libQt5Gui.so.5
#10 0x00007f74affa934d in QShortcutMap::nextState(QKeyEvent*) () at /usr/lib/libQt5Gui.so.5
#11 0x00007f74affa9737 in QShortcutMap::tryShortcut(QKeyEvent*) () at /usr/lib/libQt5Gui.so.5


Possible duplicates by query: bug 418539, bug 418477, bug 418468, bug 418367, bug 418359.

Reported using DrKonqi
Comment 1 Xaekai 2020-03-07 04:47:50 UTC
Created attachment 126647 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 David Edmundson 2020-06-19 15:09:06 UTC

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