search

input-leap / input-leap

Open-source KVM software
Other
4.4k stars 190 forks source link

Wrong Key gets transmitted (Windows to Mac) #2077

Open colenio-mhe opened 3 weeks ago

colenio-mhe commented 3 weeks ago

What happened?

Hey everyone.

I just upgraded from Barrier 2.4.x to InputLeap 3.0.3 it seems like mostly everything is working but strangely when im on my Mac and Type . (dot) I get a , (comma).

My Windows 11 PC is the Server and the Mac is the Client.

After that I checked other Keys to:

Key Pressed Key on Mac (Numlock On) Key on Mac (Numlock Off)
. , . (expected)
# 3 # (expected)
alt-gr + < | (expected) 7

I wrote (expected) to the key that should have been send (regardless of numlock on/off)

Using a Keyboard tester I saw that it seems that most keys send are the numpad ones. So pressing 1234... on the main row activate the numpad ones.. Pressing . activates the , on the numpad (german layout). After disabling num on the Keyboard it works as expected, obvioulsy numpad now doesnt work. Numpad fix didn't change anything for me.

Is this a bug or am i missing some setting?

Thanks!

Version

v3.0.2

Git commit hash (if applicable)

No response

If applicable, where did you install Input Leap from?

GitHub binaries

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

Windows, macOS

If applicable, are you using Wayland or X11?

No response

What OS versions are you using?

Windows 11 (Server) macOS 15.1 (M1) (Client)

Relevant log output

No response

Any other information

German Keyboard Layout

matthewtai commented 3 weeks ago

+1 Win11 Server, macOS client Experiencing more or less the same thing, and I couldn't get it to register certain strokes in the Mac client. E.g. = cannot be registered, but + (shift + =) does get registered

EN(US) on Win11 > EN (US) on macOS Sonoma 14.7

Tried both v3.02 and v3.01, same issue, seems to be triggered when Num Lock is on

c2ho commented 3 weeks ago

More or less the same here with a Windows 11 server-side and macOS 15.0.1 client-side on 7e5889d

I am using the german layout on all sides. Disabling NumPad seems to circumvent the behavior.

Also some other keys or combinations don't work, don't know if that's linked to my RDP sessions. I'll try to add them if I encounter them as I do not remember what wasn't working after the weekend :smile:

colenio-mhe commented 3 weeks ago

It nearly does but if you disable NumPad you cant make | anymore, you then get a 7. (And {}, [] ...) So keys that need alt-gr

right now I downgraded to barrier 2,4 on my mac that fixed it. So Inputleap 3.0.2 on Windows (Server) to barrier 2.4 on macOS (Client)

Edit: Still speaking for german layout on both sides

Edit2: seems like downgrading to barrier 2.4 works for any layout!

taylankasap commented 1 week ago

E.g. = cannot be registered

= sends backspace for me 😄

Edit: It's not backspace, it's the Clear key https://deskthority.net/wiki/Clear_key

Edit 2: Just noticed F13-F16 keys started working on the MacOS client when this bug happens. They were not working before.

Edit 3: Not sure at what point this started but now the = key is not working on the linux server and is working on the macos client.

Shira-3749 commented 6 days ago

It's even more broken with a czech keyboard layout 😞