Bug 492289 - META + V Shortcut to open clipboard history spontaneously loops itself
Summary: META + V Shortcut to open clipboard history spontaneously loops itself
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: Clipboard (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: gagepeterson182
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-27 22:56 UTC by gagepeterson182
Modified: 2024-08-31 00:27 UTC (History)
1 user (show)

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


Attachments
Meta+V Bug (3.21 MB, video/mp4)
2024-08-28 01:31 UTC, gagepeterson182
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gagepeterson182 2024-08-27 22:56:02 UTC
SUMMARY
When pressing the "Show clipboard items at mouse position" shortcut (Meta+V), the window continously opens and closes itself, disrupting the mouse from being able to interact with any part of the desktop. The loop will not stop until I kill plasmashell manually and restart it.

STEPS TO REPRODUCE
1. Boot Into KDE Plasma via login-manager (Wayland or X11)
2. Press Meta+V to show clipboard history

OBSERVED RESULT
Infinite looping window, effectively crashing plasmashell.

EXPECTED RESULT
show singular window for clipboard history and select previous clipboard to restore.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.6-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-9400F CPU @ 2.90GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
ADDITIONAL INFORMATION
The widget in the panel works perfectly, the problem only occurs from the popup window.
Comment 1 Nate Graham 2024-08-28 01:06:14 UTC

*** This bug has been marked as a duplicate of bug 489259 ***
Comment 2 gagepeterson182 2024-08-28 01:31:40 UTC
Created attachment 173017 [details]
Meta+V Bug

This is a Visual Reference (screen recording) of the bug
Comment 3 Nate Graham 2024-08-28 02:36:12 UTC

*** This bug has been marked as a duplicate of bug 489259 ***
Comment 4 gagepeterson182 2024-08-28 02:44:04 UTC
(In reply to Nate Graham from comment #3)
> 
> *** This bug has been marked as a duplicate of bug 489259 ***

Please stop marking this as a duplicate. The behavior of the bugs are entirely different, the bug I am reporting does not forcefully crash plasmashell, rather it soft-locks the user forcing them to restart plasmashell. The key only needs to be pressed once and the compositor is irrelevant, the behavior is the same on Xorg (X11) or Wayland.
Comment 5 Nate Graham 2024-08-29 20:01:21 UTC
Oh, sorry.
Comment 6 Nate Graham 2024-08-29 20:03:19 UTC
I'm unable to reproduce this in git master (which will become Plasma 6.2 in a little over a month), quite possibly because what Meta+V does has completely change for Plasma 6.2: now instead of opening a QMenu, it opens a miniaturized version of the Plasma widget, so the two share code and UI styling.

Is there any chance you can test out current git master from the kde-unstable repo to see if this fixes the issue for you too? If not, let's wait for Plasma 6.2.
Comment 7 gagepeterson182 2024-08-30 01:38:22 UTC
(In reply to Nate Graham from comment #6)
> I'm unable to reproduce this in git master (which will become Plasma 6.2 in
> a little over a month), quite possibly because what Meta+V does has
> completely change for Plasma 6.2: now instead of opening a QMenu, it opens a
> miniaturized version of the Plasma widget, so the two share code and UI
> styling.
> 
> Is there any chance you can test out current git master from the
> kde-unstable repo to see if this fixes the issue for you too? If not, let's
> wait for Plasma 6.2.

I see the kde-unstable repo but I'm not sure how to install the packages from it and replace the regular plasma packages. I am fully updated to the newest release from the normal arch linux repo, is the version from the arch linux repo have conflicting code with the plasma-workspace package?
Comment 8 Nate Graham 2024-08-30 15:42:47 UTC
That's ok, don't blow up your system over it. I'm fairly sure this can no longer happen as described due to the change in Plasma 6.2 I mentioned. Let's close it for now. However if after updating to Plasma 6.2, you do find that you can still reproduce the issue, feel free to re-open this ticket. Thanks!
Comment 9 gagepeterson182 2024-08-31 00:27:56 UTC
Okay, thank you so much! I'll make sure to try it later on