-
Notifications
You must be signed in to change notification settings - Fork 139
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
Bug: Kanata doesn't automatically register bluetooth keyboard when it connects the second time #1390
Comments
Kanata is deregistering the device because it gets a "no device" error. Lines 158 to 166 in 70f5a85
The discovery of devices is based on new files created in the filesystem path of Lines 708 to 712 in 70f5a85
Perhaps you can play around with adding new watch types. But would need to be wary of the watched event being too noisy and causing a lot of extra processing. https://docs.rs/inotify/latest/inotify/struct.WatchMask.html#associatedconstant.MODIFY |
Since I found some time I did some more testing with the directions you gave me. I started by somewhat brute forcing Why (I think) the addition of
|
Requirements
Describe the bug
When using a bluetooth keyboard (Logitech MX Mechanical) kanata fails to notice the keyboard after connecting the second time. The device will be detected if kanata is restarted or another device is registered, prompting kanata to also notice and register the bluetooth device.
This behaviour does not occur for a wired keyboard.
Relevant kanata config
To Reproduce
Expected behavior
Kanata notices the new input device and registers it.
Kanata version
kanata 1.7.0
Debug logs
Operating system
Linux (Arch, kanata-bin from AUR)
Additional context
The bluetooth keyboard in question is the
MX MCHNCL Keyboard
in the logs.Near the middle of the debug log I unplug the
Hewlett-Packard
(wired) keyboard (/dev/input/event21
) and plug it back in. After which both the wired and bluetooth keyboards get picked up and registered.I encountered the bug because my keyboard can switch between multiple devices, which has the same effect as disconnecting and reconnecting when switching from and to the device. (The test for the bug report was done by turning the keyboard off instead of switching devices to make the test more generally reproducible.)
The text was updated successfully, but these errors were encountered: