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
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?
(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.
Does any of this work in a new clean user account?
(In reply to Nate Graham from comment #3) > Does any of this work in a new clean user account? It does not.
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.
(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.
I asked the CachyOS team, but they didn't respond. However, I just tried to replicate this bug on Fedora 42 KDE and I encountered this bug there as well. So it doesn't seem likely to me that it's just a packaging issue. Would you mind looking into this after all?
I cannot reproduce it in Fedora KDE 42. :/
Alright, so after a little more playing around, it turns out it does work, but only if I set the shortcut to global, not in the ‘Shortcut’ column. Which is still a bug in my eyes, as it used to work fine in the first column. And even if it's an intented change, it should be made more clearly that ‘Global’ is now the preferred option.
Ah, well-spotted! That means you were setting it as an application-local shortcut. In this case the application is Plasma, so it would only work when a part of Plasma had focus, but not at other times. We should hide all the "Shortcut" and "Alternate" columns here since only global shortcuts make sense for this UI. I'll throw it on the to-do list.
Thanks in advance! 🙂
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5608
Git commit 1d3fe2ac0c0e640f0b66ec1e1d34f0e0196bbd7d by Akseli Lahtinen. Committed on 19/06/2025 at 16:00. Pushed by akselmo into branch 'master'. Klipper: Remove local Configure Klipper action This action would cause the shortcuts configuration menu to show both local and global shortcuts, which makes no sense due to Klipper being a globally accessed application. This action is only used in cases where Klipper will be it's own application with a normal window, similar to applications like Dolphin, Kate, etc.. But Klipper is never used this way. Currently only place where you can use this action is the configuration menu itself, where it does nothing, since the menu is already open. So let's just remove it. This also makes sure users do not accidentally select "Shortcut/Alternate" instead of "Global Shortcut/Alternate" for their shortcuts. See the related bug for context. FIXED-IN: 6.4.1 M +0 -6 klipper/klipper.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/1d3fe2ac0c0e640f0b66ec1e1d34f0e0196bbd7d
Git commit d286dce389e90428f04115fdb631a381d4942641 by Akseli Lahtinen. Committed on 19/06/2025 at 17:46. Pushed by akselmo into branch 'Plasma/6.4'. Klipper: Remove local Configure Klipper action This action would cause the shortcuts configuration menu to show both local and global shortcuts, which makes no sense due to Klipper being a globally accessed application. This action is only used in cases where Klipper will be it's own application with a normal window, similar to applications like Dolphin, Kate, etc.. But Klipper is never used this way. Currently only place where you can use this action is the configuration menu itself, where it does nothing, since the menu is already open. So let's just remove it. This also makes sure users do not accidentally select "Shortcut/Alternate" instead of "Global Shortcut/Alternate" for their shortcuts. See the related bug for context. FIXED-IN: 6.4.1 (cherry picked from commit 1d3fe2ac0c0e640f0b66ec1e1d34f0e0196bbd7d) Co-authored-by: Akseli Lahtinen <akselmo@akselmo.dev> M +0 -6 klipper/klipper.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/d286dce389e90428f04115fdb631a381d4942641