Bug 489462 - Closing the clipboard history with Meta+V after interacting with it causes plasmashell to crash.
Summary: Closing the clipboard history with Meta+V after interacting with it causes pl...
Status: RESOLVED DUPLICATE of bug 489259
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard (show other bugs)
Version: 6.1.1
Platform: NixOS Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-29 21:22 UTC by Naxdy
Modified: 2024-07-09 07:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Naxdy 2024-06-29 21:22:47 UTC
SUMMARY
Closing the clipboard history with Meta+V after using the search box causes plasmashell to crash.

STEPS TO REPRODUCE
1. Open the clipboard history with Meta+V
2. Press space (or literally anything else)
3. Press Meta+V again

OBSERVED RESULT
Plasmashell crashes

EXPECTED RESULT
Clipboard history closes, without Plasmashell crashing

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS
(available in About System)
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Closing the clipboard history with Meta+V when the search box is empty also causes it to crash, if a search has previously happened. Selecting an item after searching does NOT cause a crash.

Unclear if this is a regression, or if I've just noticed it (I don't search often without selecting the item).
Comment 1 Naxdy 2024-06-29 21:27:48 UTC
Actually, even hovering over elements and then closing it causes it to crash. Seems like any kind of interaction can cause this.
Comment 2 Nate Graham 2024-07-02 20:03:38 UTC
If something crashed, we need a backtrace. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.

If plasmashell exited but didn't actually crash, it may be Bug 489259.
Comment 3 Naxdy 2024-07-09 07:29:47 UTC
Yep, looks like it's that one.

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