Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keysym mappings shift when ckb-next GUI tool opens; corrected by unplugging & replugging keyboard #391

Open
spillner opened this issue Mar 6, 2021 · 0 comments

Comments

@spillner
Copy link

spillner commented Mar 6, 2021

I've got a Corsair Strafe running the latest firmware (3.08). For the most part ckb-next works really well on my system, but there's one annoyance every time I have to restart my X session (which fortunately isn't often): I have the userspace side of ckb-next set to load on startup, and every time it does the keyboard LEDs flash briefly, I assume by design. Exactly at that moment, even if I'm switched to a virtual console instead of watching X/KDE start up, I get the following remappings:

Numeric keypads:

Keypad / sends KP_Divide and Insert
Keypad enter sends KP_Enter and Down

Top three (Print Scrn / Scroll Lock / Pause Break):

Print Scrn sends Print and Delete
Scroll Lock sends Scroll_Lock event, but never toggles lock status (always off, keyboard LED agrees)
Pause/Break sends Pause and keysym 0 ("No Symbol")

Middle pack of six:

Insert sends Insert and keysym 0 ("No Symbol")
Home sends Home and Pause
Page Up sends Prior and KP_Divide
Delete sends Delete and keysym 0 ("No Symbol")
End sends End and Super_L
Page Down sends Next and Menu

Arrow keys:

Up sends Up and Print
Left sends Left and Alt_R
Down sends Down and Super_R; occasionally this is interpreted in the terminal as just "B" rather than ^B (e.g. if I press the down arrow 20 times I might get 8 instances of Down and 12 of B.)
Right sends Right and keysym 0 ("No Symbol")

Modifiers:

Right Ctrl sends R_Ctrl and Page Down
Right Alt sends R_Alt and keypad Enter

Keys not listed above are unaffected. The issue is usually corrected (all keysym mappings go back to normal) by unplugging and reconnecting the keyboard, but on a few occasions I've had to do a keyboard reset (unplug, hold down Esc, reconnect, unplug again, reconnect normally). Note that this solves the issue without having to change anything on the software side, i.e. no restart of ckb-next, its daemon, or X11/window manager is required.

I'm running Linux 5.10.18, X.org 1.20.10, KDE 5.79 with Qt 5.15.2 and Plasma 5.21.1 (over X11, not Wayland), and the latest ckb-next from git. I don't have any mappings loaded in ckb-next that affect any of the keys listed above, nor any xmodmap or other remappings active. I'm set to a standard U.S. PC-104 key layout with nothing else besides ckb-next that might be intercepting hardware key events before they get to X.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant