@nclarius
Alright, I'm seeing the same effect of interference with other keyboard shortcuts on a physical machine as well as the (Boxes/qemu) VM that I was using to test.
The VM was running KDE Neon User Edition, installed just a couple of days ago.
The physical machine is a 2007 white MacBook with Fedora 36 KDE spin freshly installed.
Both machines have Kinto.sh installed to remap the keyboard to act like a Mac, but even with that completely disabled the interference is happening. So I don't think it has anything to do with Kinto or xkeysnail
, the Python app it uses to remap the keyboard input.
What I'm seeing:
With the Kwin script disabled, I can reliably trigger things like krunner
, the main application launcher menu, and a "search" dropdown that mimics Spotlight from macOS. The shortcuts are:
Ctrl+Shift+Space (KDE app launcher menu)
Alt+Space (krunner)
Alt+F1 (Spotlight search clone widget)
These are the actual shortcuts the widgets are set to use, but with Kinto active they remap to different physical keys on the keyboard.
When I have the Kwin script activated, the success rate for triggering any of these shortcuts falls to around 30-50%. In other words, with the script deactivated I can sit here and hold down Cmd+Shift (on the real MacBook) and hit Space over and over, and the KDE app launcher menu will appear and disappear with 100% reliability. Cmd+Space will activate the Spotlight clone, and hide it. Option(Alt)+Space will reveal krunner
.
But once I activate the Kwin script these things will either not activate at all, or I'll see a flash as if it was about to activate, but then it goes away without fully opening.
There doesn't seem to be any corresponding effect on the speed or responsiveness of Alt+Tabbing, even with Kinto remapping physical Cmd+Tab to the Alt+Tab logical shortcut.
I can also go crazy doing shortcuts like Cmd+T (new tabs) and Cmd+N (new window), Cmd+W (close tab/window), and there seems to be no issue with such things.
Working theory: This has something to do with the described shortcuts somehow taking focus away from the current window. In other words, maybe triggering these things that are appearing from the top panel (Whitesur Dark global theme applied) is generating some kind of window activation event.
Yeah, seems to be some sort of window focus problem, because when I use the mouse to access the KDE app launcher menu or the Spotlight clone from their icons on the top bar, I also see an unreliable response to the mouse clicks. As I type in this browser window there is a highlighted border around the text box I'm typing in, and when I click on the icons on the top bar that will flash, and more often than not the focus will immediately return to the browser window rather than opening the item in the top bar.
Other icons in the top bar like clipboard indicator, volume and WiFi icons are exhibiting the same behavior. Seems to be a general problem with the Kwin script not wanting to let windows lose focus to these objects living in the top panel. (If you're using the typical default KDE setup these things will mostly be in your "bottom" panel.)
I haven't even taken a look at the code yet, so I can't offer any specific ideas at the moment as to why this is happening or how to fix it.