Open dlobue opened 3 years ago
Did you solve it? Today I read your issue because I was looking the same solution and decided to look on KDE configuration after I notice you use too. Actually I notice that (my) problem** was on KDE and is not a bug on barrier.
Same for me. Debian 11 bullseye x86_64 Linux 5.10.0-6-amd64, KDE 5.78.0 / Plasma 5.20.5. Using last Barrier release 2.3.3 .
I'm also seeing this on NixOS using FVWM, which definitely doesn't eat the keypress. It was easy enough to work around by exporting the config to a text file and adding it there, but it's inconvenient.
I had this issue but I haven't it any more. Try add this config to your screen.
meta = altgr
altgr = shift
I tried adding these to my config, but neither works. It's quite unfortunate.
keystroke(Control+y) = keystroke(Super+Shift+z,Phils-MacBook-Pro.local)
keystroke(Control+y) = keystroke(Meta+Shift+z,Phils-MacBook-Pro.local)
Without Shift, both work, which is really weird. With just Shift+z
, Shift is not sent at all.
EDIT: For some reason, Z
has to be uppercase! This works okay-ish (although far from perfect, you gotta release Ctrl to press Ctrl-Z after)
keystroke(Control+y) = keystroke(Meta+Shift+Z,Phils-MacBook-Pro.local)
Which also works alongside
ctrl = super
super = ctrl
Has anyone found a workaround yet?
Regarding a workaround, as I said above (emphasis added):
I'm also seeing this on NixOS using FVWM, which definitely doesn't eat the keypress. It was easy enough to work around by exporting the config to a text file and adding it there, but it's inconvenient.
More explicitly:
keystroke(Alt+Super+Control+j) = switchToScreen(other)
. Note also his issues with shift; apparently if you want to do something with the Shift modifier, you need to capitalize the key.Sadly, AFAICT there's no way to import the config back, so you have to either make further updates in the text file (which honestly, I prefer anyway), or else re-export and fix Super every time you update your configuration.
Describe the bug
When configuring keystrokes in the hotkeys gui, the windows/super key is not captured. This happens when defining the initiating hotkey, as well as when defining keystrokes for the resulting action.
To Reproduce
Steps to reproduce the behavior:
New
to create a new hotkeySuper+v
keystroke(v)
Expected behavior
I expect the captured keystroke to read
keystroke(Super+v)
Desktop (please complete the following information):
Additional context
I am not running Wayland. I'm running kde/plasma 5 on x11. I discovered this issue when I was creating a hotkey to map ctrl+v to super+v for my mac client.