`Wndw+Space` bugs

[geofflittle]

Describe the bug There are three issues:

1. Physical Wndw+Space is mapped to Alt+F1 in all applications,
2. Physical Wndw+Space executes Alt+F1 and also produces a P character, and
3. Physical Wndw+Tab somehow maps to either Alt+F1 or Alt+RC, I can't tell.

Expected behavior

1. Physical Wndw+Space is expected to map to Ctrl+Space (I think),
2. Physical Wndw+Space shouldn't produce a P character in the Terminal application, and
3. Physical Wndw+Tab is expected to map to Alt+Tab (I think) to open the app switcher.

Install Type: Bare Metal Distro: Ubuntu 22.04 DE: Gnome Branch: N/A, not installed from source Commit: N/A, not installed from source

Logs and status if relevant Probably not relevant, I think the linked gif will be enough but let me know if you need logs.

Screenshots I've included a gif of a screencast in which I execute three tests.

1. With focus in the Ulauncher preferences, I attempt to set the Ulauncher hotkey and press Wndw+Space, Alt+F1 is received (we can see this from the screenkey output), but the hotkey is set to Alt+RC (I'm not sure if RC is the correct term here for what's shown in the video as Control R, please correct me if I'm wrong).
2. With focus on the Terminal application, I press Wndw+Space, Alt+F1 is received, Ulauncher opens (I'm not sure what's the relationship between Alt-F1, what is received, and Alt+Control R, what's listed in the Ulauncher prefs), and a P character is produced.
3. I press Wndw+Tab, Alt-Tab is received, and Ulauncher opens (similarly, I don't understand the relationship between Alt+Tab, what I pressed, and Alt+Control R, what's listed in the Ulauncher prefs).

Additional context I have a windows keyboard (my bottom row is Ctrl Wndw Alt Space Alt Wndw Fn Ctrl) and I have muscle memory from a Mac (Cmd+C {V} copies {pastes}).

I'm ultimately trying to get the Wndw+Space keyphrase to open Ulauncher, and nothing else, and Wndw+Tab to open the application switcher, and nothing else.

Thanks, Geoff

[RedBearAK]

@geofflittle

I'm not the dev, but I've been messing with Kinto for a long time and I'm using Ubuntu 22.04.

You're doing a pretty good job describing the physical and logical variations of the keys, so thanks for that. But something seems a bit off.

My Acer PC laptop keyboard is physically Ctrl Fn Win(Super) Alt Space Alt Menu Ctrl Arrows on the bottom. When Kinto is active, in GUI apps with "Windows" set as the keyboard type, this becomes logically Win(Super) Fn Alt Ctrl(Right) Space Ctrl(Right) Alt Win(Super) Arrows. In terminals it becomes Ctrl(Left) Fn Alt Ctrl(Right) Space Ctrl(Right) Alt Ctrl(Left) Arrows. There's no Win(Super) modifier active while in terminal apps.

So ordinarily I would expect that the key right next to the spacebar (physical Alt on PC keyboards) is the key that is emitting Ctrl and acting as a virtual Command key.

But you keep saying that you're using the physical Windows key to do Cmd+Tab and such. So... are you sure you have the correct keyboard type selected (using the Kinto GUI app or the Kinto tray icon)? Did you press the key 2nd to the left of the spacebar, or the Alt key just to the left of the spacebar during setup? Pressing the 2nd key (usually Win/Super on a PC keyboard) is how Kinto figures out which keyboard type to use. That key would be Option/Alt on an Apple keyboard, so Kinto may have swapped the modifiers because it thinks you're using an Apple keyboard.

You can change it from the Kinto tray icon or the Kinto GUI app menu. Or you can re-run the Kinto installer and make sure you press the 2nd key to the left of the spacebar. Hopefully that will fix some of this.

The issue of "P" appearing in the terminal is not something I've ever encountered, but probably stems from having the wrong keyboard type active.

To make the Cmd+Space shortcut work with Ulauncher try stopping Kinto from the tray icon (or GUI app menu) and using the physical Alt+F1 keys to enter the shortcut, or even just using the logical remapped keys. On a typical PC keyboard that would be Win(Super)+F1. But I usually have to disable Kinto to get Ulauncher to accept the shortcut. Then when you restart Kinto it should work as expected.