Bug 440153 - Plasma crashed when i selected the location line in ".desktop -> Edit application" and tried to copy it with Ctrl + C
Summary: Plasma crashed when i selected the location line in ".desktop -> Edit applica...
Status: RESOLVED DUPLICATE of bug 420178
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Properties dialog (show other bugs)
Version: 5.83.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2021-07-22 12:05 UTC by Lyubomir
Modified: 2022-01-19 20:24 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lyubomir 2021-07-22 12:05:15 UTC
Application: plasmashell (5.22.3)

Qt Version: 5.15.2
Frameworks Version: 5.83.0
Operating System: Linux 5.11.0-22-lowlatency x86_64
Windowing System: X11
Drkonqi Version: 5.22.3
Distribution: Ubuntu 21.04

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

1. Open start menu
2. Search for flameshot
3. Right click with the mouse the entry and select "Edit application"
4. Click over the location path two times with the left button of the mouse in order to select all of the path/location
5. Press Ctrl + C to copy
6. Plasma crashed

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x00007faa30eb94a4 in QQuickShortcutContext::matcher(QObject*, Qt::ShortcutContext) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5
#5  0x00007faa3701835f in QShortcutEntry::correctContext (this=0x5611663d9da0) at kernel/qshortcutmap.cpp:79
#6  QShortcutMap::find (this=this@entry=0x5611652fc8f8, e=e@entry=0x7ffd8b147220, ignoredModifiers=ignoredModifiers@entry=0) at kernel/qshortcutmap.cpp:457
#7  0x00007faa3701b2c4 in QShortcutMap::nextState (this=this@entry=0x5611652fc8f8, e=e@entry=0x7ffd8b147220) at kernel/qshortcutmap.cpp:372
#8  0x00007faa3701c589 in QShortcutMap::tryShortcut (this=this@entry=0x5611652fc8f8, e=e@entry=0x7ffd8b147220) at kernel/qshortcutmap.cpp:328
#9  0x00007faa36fc4532 in QWindowSystemInterface::handleShortcutEvent (window=0x7ffd8b147220, timestamp=1045198460, keyCode=67, modifiers=..., nativeScanCode=54, nativeVirtualKey=99, nativeModifiers=8196, text=..., autorepeat=false, count=1) at kernel/qwindowsysteminterface.cpp:477
#10 0x00007faa36fe7a0f in QGuiApplicationPrivate::processKeyEvent (e=0x56116d6e5400) at kernel/qguiapplication.cpp:2395
#11 0x00007faa36fc0e2c in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#12 0x00007faa31c90a6e in xcbSourceDispatch (source=<optimized out>) at qxcbeventdispatcher.cpp:105
#13 0x00007faa3502b8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007faa3507ed28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007faa35029023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007faa36c60204 in QEventDispatcherGlib::processEvents (this=0x5611653e3b80, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#17 0x00007faa36c0511b in QEventLoop::exec (this=this@entry=0x7ffd8b147560, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#18 0x00007faa36c0d604 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#19 0x00007faa36fdf520 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867
#20 0x00007faa378e86f9 in QApplication::exec () at kernel/qapplication.cpp:2824
#21 0x0000561163817e08 in main (argc=<optimized out>, argv=0x7ffd8b1476d0) at ./shell/main.cpp:254
[Inferior 1 (process 751418) detached]

Possible duplicates by query: bug 438133, bug 434128, bug 428949, bug 424142, bug 424120.

Reported using DrKonqi
Comment 1 Ahmad Samir 2021-08-04 22:51:51 UTC
I don't see anything kio-related in that backtrace..
Comment 2 Nicolas Fella 2022-01-19 20:24:21 UTC

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