Bug 501632

Summary: History pop-up doesn't show at cursor location
Product: [Plasma] plasmashell Reporter: Heimen Stoffels <vistausss>
Component: Clipboard widget & pop-upAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: nate
Priority: NOR    
Version: master   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Heimen Stoffels 2025-03-17 11:59:40 UTC 
SUMMARY
I set a shortcut to open the history at the cursor position, but the history menu never shows.

STEPS TO REPRODUCE
1. Open the Klipper shortcut settings
2. Set a shortcut for it to open at the cursor position
3. 

OBSERVED RESULT
It doesn't open the history menu.

EXPECTED RESULT
It should show the history menu.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: CachyOS (based on Arch Linux)
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-03-17 17:01:04 UTC 
There should be a default shortcut set, with a value of Meta+V (Meta being the Windows key on most keyboards). Does that not work for you?
Comment 2 Heimen Stoffels 2025-03-17 18:03:30 UTC 
(In reply to Nate Graham from comment #1)
> There should be a default shortcut set, with a value of Meta+V (Meta being
> the Windows key on most keyboards). Does that not work for you?

That doesn't work. But I don't like that shortcut anyway, so I set a different one that also doesn't work. So either way, none of the shortcuts (default or not) bring up the history menu under the cursor location.
Comment 3 Nate Graham 2025-03-19 18:34:53 UTC 
Does any of this work in a new clean user account?
Comment 4 Heimen Stoffels 2025-03-19 18:37:43 UTC 
(In reply to Nate Graham from comment #3)
> Does any of this work in a new clean user account?

It does not.
Comment 5 Nate Graham 2025-03-19 18:39:59 UTC 
In that case it seems like there is a serious problem somewhere: either a code problem, or perhaps a problem with your distro's packaging of this software, or perhaps  a configuration at the system level that you made in the past

I can't reproduce it on my system and this is the only bug report we have about it, so at this point I'm leaning towards one of the latter two options. I'd recommend asking your distro's packagers or QA team for help with this.
Comment 6 Heimen Stoffels 2025-03-19 18:42:16 UTC 
(In reply to Nate Graham from comment #5)
> In that case it seems like there is a serious problem somewhere: either a
> code problem, or perhaps a problem with your distro's packaging of this
> software, or perhaps  a configuration at the system level that you made in
> the past
> 
> I can't reproduce it on my system and this is the only bug report we have
> about it, so at this point I'm leaning towards one of the latter two
> options. I'd recommend asking your distro's packagers or QA team for help
> with this.

Thanks. It's fairly clean Plasma install, so I don't think it's a configuration issue, but it could be a packaging issue. I'll ask them about it and will point them to this bug.