You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This state that the keyboard is in is easily and repeatedly reproducible if you use a USB 3.0 switch like the Sabrent USB-SW30. Clicking the switch puts the keyboard in the unusable state.
Result
Until you unplug the keyboard, it's in an unusable state:
All mappings revert to stock
First keystroke is captured
Subsequent keystrokes are ignored
Keyboard remains in an unrecoverable state
The first key that is pressed is captured, but it is done so with the standard out of the box keyboard layout.
For instance, my Caps Lock key is set to MO(2). But, when my keyboard gets into this state, the key reverts back to a standard Caps Lock key. Pressing it as the first key turns Caps Lock on, and subsequent keypresses with another keyboard will output uppercase characters. Turning Caps Lock on/off with the other keyboard will revert it back to lowercase.
Note: I have personally reproduced this issue with:
macOS
Windows 10
Windows 11
Arch Linux (Kernel 5.18.12)
The text was updated successfully, but these errors were encountered:
Unfortunately, it appears that a bug with these keyboards has all but been ignored for a few months now.
Here's a few excerpts of a comment I made alongside many others in response to the announcement posted by @just-another-jxliu:
Issue
Visualizing The Issue
Reproduction Steps
Result
The text was updated successfully, but these errors were encountered: