#2390·input-leap

Switching screens while a windows console is focused toggles keyboard languages when alt+shift hotkey is enabled on windows machine.

Author: dotacowCreated Jun 13, 2026Updated Jul 4, 2026

What happened?

steps to reproduce:

1- have at least one windows machine with input leap running 2- configure windows machine to have at least 2 keyboard languages 3- configure windows machine to use alt+shift as a language toggle 4- focus a classic windows console (cmd) or an application that runs said cmd. *windows terminal & windows powershell don't seem to have this problem. 5- switch screens. you will notice that the language gets switched.

Version

v3.0.2

Git commit hash (if applicable)

No response

If applicable, where did you install Input Leap from?

N\A

What OSes are you seeing the problem on? (Check all that apply)

Windows

If applicable, are you using Wayland or X11?

X11 on the client, although this is irrelevant.

What OS versions are you using?

Server: Windows 10 Client: Debian 6.1.174-1

Relevant log output

bash
N\A

Any other information

I suspect (after some surface level research, I don't have much knowledge in windows subsystems) that this happens due to all modifier keys (Alt, Shift, Ctrl, Win) getting the key release signal upon switch (which is correct, not doing so would cause them to get stuck), but for some reason the conhost.exe catches and interprets said release as an alt+shift trigger.

I believe the reason only the classic cmd causes this, is because it uses Cooked/Canonical Mode, causing some windows subsystem to catch and interpret the key releases.

I'll try a couple of approaches to fix this, if any succeed I'll PR.