Bug: kanata wintercept doesn't send anything on any keyboard and mouse if you disconnect and reconnect a mouse input device

[flamingjupiter]

Requirements

• I've searched platform-specific issues, issues and discussions to see if this has been reported before.

Describe the bug

Just as the title says, if you disconnect and reconnect a mouse/mouse like input device, kanata stops sending any input from any keyboard and/or mice, except for cursor input and mouse buttons from hardware ids not listed on windows-interception-mouse-hwid defcfg option.

Kanata still shows when you change layers and all that on its terminal, but you won't actually send anything. Then you have to move the cursor with any mouse/cursor input device (it doesn't block cursor input/movement) to close kanata's window using only mouse buttons, because nothing else will actually input on the system (I move the cursor to kanata's terminal window and just click on the close button). Then you can input anything normally, albeit without kanata modifications, because it isn't running.

I need to restart the computer in order to use kanata normally again. If I disconnect/reconnect the mouse, be it with kanata opened or closed, this bug will happen over and over whenever I open/have kanata running on my system, until I restart it.

I still haven't tested what happens if I connect another keyboard (so 2 keyboards in total) and list only one of them on the windows-interception-keyboard-hwids, to see if the keyboard that's not listed retain input capability. And putting the computer to sleep and waking up doesn't cause this bug. Didn't test hibernating the computer as well.

I will also test disconnecting the mouse and not reconnecting, to see if the bug happens or not.

Relevant kanata config

No response

To Reproduce

Expected behavior

.

Kanata version

kanata v1.6.0-prerelease-1

Debug logs

No response

Operating system

Windows 11

Additional context

No response

[flamingjupiter]

I will also test disconnecting the mouse and not reconnecting, to see if the bug happens or not.

Merely disconnecting the mouse is enough to cause the bug. I'm typing this with kanata closed at the moment.

[flamingjupiter]

Couldn't replicate the issue on another machine, seems there's a conflict with another application running. Will investigate.

[jtroo]

Yea I haven't been able to reproduce the issue myself on the machine where I use Interception

[flamingjupiter]

Well, now I can't replicate the issue on any machine, no matter what I do or run. Strange. It kept invariably happening for more than a month, then I didn't do anything (besides restarting the pc, but that I needed to do everytime) and it doesn't happen anymore. Should I just close this issue?

[jtroo]

Hmm maybe a Windows update broke and then fixed it? If we can't reproduce then no point keeping open 🤷