Keys being pressed multiple times, especially when typing at speed. #113

New issue

Closed

opened 2026-02-20 08:20:27 -05:00 by deekerman · 39 comments

deekerman commented 2026-02-20 08:20:27 -05:00

Owner

Copy link

Originally created by @IanSeyler on GitHub (Feb 13, 2025).

Originally assigned to: @ym on GitHub.

As the title says - key presses are sometimes being registered multiple times on the JetKVM host system.

This was originally posted in the Discord on Jan 14, 2025 by user Dax.

I've tested from macOS (15.3) / Safari (18.3) to a JetKVM attached to a Windows 10 system

Sometimes I can also hit a key and it will repeat continously until I hit another key.

Originally created by @IanSeyler on GitHub (Feb 13, 2025). Originally assigned to: @ym on GitHub. As the title says - key presses are sometimes being registered multiple times on the JetKVM host system. This was originally posted in the Discord on Jan 14, 2025 by user Dax. I've tested from macOS (15.3) / Safari (18.3) to a JetKVM attached to a Windows 10 system Sometimes I can also hit a key and it will repeat continously until I hit another key.

deekerman 2026-02-20 08:20:27 -05:00

• closed this issue
• added the
  component: hid/keyboard
  status: working-in-progress
  labels

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@branwall commented on GitHub (Feb 14, 2025):

Reporting that I have the same issue when using Windows 11 on both Firefox and Chrome to get into a JetKVM attached to a Windows 10 system.

Some keys appear to duplicate several moments after their initial press. For example:

This is how I type a sentence

appears as:

This sis how I tytpe a senetence.

where the bolded letters are the duplicate presses being inserted erroneously. If I type slowly (<40 WPM), I do not see this issue appear.

@branwall commented on GitHub (Feb 14, 2025): Reporting that I have the same issue when using Windows 11 on both Firefox and Chrome to get into a JetKVM attached to a Windows 10 system. Some keys appear to duplicate several moments after their initial press. For example: > This is how I type a sentence appears as: > This **s**is how I ty**t**pe a sen**e**tence. where the bolded letters are the duplicate presses being inserted erroneously. If I type slowly (<40 WPM), I do not see this issue appear.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@ozgith commented on GitHub (Feb 14, 2025):

Same issue when using Safari on iPad to get to JetKVM attached to Ubuntu 24.04 LTS. Keys start duplicating when I try to enter my password on the logon screen no matter how slow I try. Keys repeat indefinitely, making it impossible to logon.

@ozgith commented on GitHub (Feb 14, 2025): Same issue when using Safari on iPad to get to JetKVM attached to Ubuntu 24.04 LTS. Keys start duplicating when I try to enter my password on the logon screen no matter how slow I try. Keys repeat indefinitely, making it impossible to logon.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@shapetheLOLa commented on GitHub (Feb 17, 2025):

same issue with macos and chrome/safari/firefox

@shapetheLOLa commented on GitHub (Feb 17, 2025): same issue with macos and chrome/safari/firefox

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@ajeffco commented on GitHub (Feb 18, 2025):

Same issue when browsing to the JetKVM from Edge on Kubuntu 24.04, JetKVM is connected to a Qotom Proxmox Server.

@ajeffco commented on GitHub (Feb 18, 2025): Same issue when browsing to the JetKVM from Edge on Kubuntu 24.04, JetKVM is connected to a Qotom Proxmox Server.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@IanSeyler commented on GitHub (Feb 19, 2025):

Tested after update and issue still exists in App 0.3.7 / System 0.2.2

@IanSeyler commented on GitHub (Feb 19, 2025): Tested after update and issue still exists in App 0.3.7 / System 0.2.2

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@stylophile commented on GitHub (Feb 19, 2025):

Same issue here after the update to 0.3.7/0.2.2. Connected host is a MacOS 15.3 system, and client device is Windows 11 with Edge browser.

@stylophile commented on GitHub (Feb 19, 2025): Same issue here after the update to 0.3.7/0.2.2. Connected host is a MacOS 15.3 system, and client device is Windows 11 with Edge browser.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@nhaneezy commented on GitHub (Feb 20, 2025):

same problem but the key repeats go on forever unless another key is pressed. so as a bad workaround i’ve had to resort to pressing the shift key after each character to stop the repeats. it’s hell during password entries on ubuntu ssh logins. i can’t see if the characters are repeat or not.

@nhaneezy commented on GitHub (Feb 20, 2025): same problem but the key repeats go on forever unless another key is pressed. so as a bad workaround i’ve had to resort to pressing the shift key after each character to stop the repeats. it’s hell during password entries on ubuntu ssh logins. i can’t see if the characters are repeat or not.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@ozgith commented on GitHub (Feb 21, 2025):

same problem but the key repeats go on forever unless another key is pressed. so as a bad workaround i’ve had to resort to pressing the shift key after each character to stop the repeats. it’s hell during password entries on ubuntu ssh logins. i can’t see if the characters are repeat or not.

Till now, I was trying the delete key to stop the repeating keys, your shift key suggestion helped me a lot. At least I can now use my jetkvm to pass the logon screen. I also tried the update, no fix.

@ozgith commented on GitHub (Feb 21, 2025): > same problem but the key repeats go on forever unless another key is pressed. so as a bad workaround i’ve had to resort to pressing the shift key after each character to stop the repeats. it’s hell during password entries on ubuntu ssh logins. i can’t see if the characters are repeat or not. Till now, I was trying the delete key to stop the repeating keys, your shift key suggestion helped me a lot. At least I can now use my jetkvm to pass the logon screen. I also tried the update, no fix.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@shayaansiddiqui commented on GitHub (Feb 22, 2025):

I am not sure if this is the same issue.
When I type, it repeats the last key indefinitely until I press SPACEBAR or DELETE

Host system is Windows 11
PC Manufacturer - Dell
Connected via USB-C to USB A on port directly on laptop (no HUB)

@shayaansiddiqui commented on GitHub (Feb 22, 2025): I am not sure if this is the same issue. When I type, it repeats the last key indefinitely until I press SPACEBAR or DELETE Host system is Windows 11 PC Manufacturer - Dell Connected via USB-C to USB A on port directly on laptop (no HUB)

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@codycaptures commented on GitHub (Feb 22, 2025):

I only have experienced this issue (so far) through remoting in from the cloud dashboard, away from local network (coffee shop in town).

When accessing jetkvm directly, or cloud dashboard from local network, I havent experienced this problem

@codycaptures commented on GitHub (Feb 22, 2025): I only have experienced this issue (so far) through remoting in from the cloud dashboard, away from local network (coffee shop in town). When accessing jetkvm directly, or cloud dashboard from local network, I havent experienced this problem

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@williamjohnstone commented on GitHub (Feb 27, 2025):

I've experienced this locally to, I'll look into it if I find the time

@williamjohnstone commented on GitHub (Feb 27, 2025): I've experienced this locally to, I'll look into it if I find the time

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@rsxm5 commented on GitHub (Mar 25, 2025):

Having this problem as well while connecting over a local network.

@rsxm5 commented on GitHub (Mar 25, 2025): Having this problem as well while connecting over a local network.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@IanSeyler commented on GitHub (Mar 25, 2025):

Issue still present in App 0.3.8 / System 0.2.3

@IanSeyler commented on GitHub (Mar 25, 2025): Issue still present in App 0.3.8 / System 0.2.3

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@Drayak335 commented on GitHub (Mar 27, 2025):

I have the same issue on Edge on Win11, running the latest App 0.3.8 / System 0.2.3 when testing locally from a Win11 laptop to another Win11, USB C to USB on Laptop., I tried changing the different Identifiers and Classes but still the same.

An interesting test I did, From the laptop I have issues, I RDP to another laptop and from there using Edge to jetKVM, I dont have the issue, I can type faster (a bit slower than my regular speed but feels more close to normal) adding the RDP in the middle than locally.

@Drayak335 commented on GitHub (Mar 27, 2025): I have the same issue on Edge on Win11, running the latest App 0.3.8 / System 0.2.3 when testing locally from a Win11 laptop to another Win11, USB C to USB on Laptop., I tried changing the different Identifiers and Classes but still the same. An interesting test I did, From the laptop I have issues, I RDP to another laptop and from there using Edge to jetKVM, I dont have the issue, I can type faster (a bit slower than my regular speed but feels more close to normal) adding the RDP in the middle than locally.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@0rsted commented on GitHub (Apr 11, 2025):

There's been some digging in this thread, and it seems like it's related to network issues.

@0rsted commented on GitHub (Apr 11, 2025): There's been some digging in [this thread](https://github.com/jetkvm/kvm/issues/325), and it seems like it's related to network issues.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@IanSeyler commented on GitHub (Apr 21, 2025):

Issue still present in App 0.3.9 / System 0.2.3

@IanSeyler commented on GitHub (Apr 21, 2025): Issue still present in App 0.3.9 / System 0.2.3

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@shapetheLOLa commented on GitHub (Apr 22, 2025):

yea, still having the same. I stopped using the device unfortunately due to this bug. I have cat 6e cables and dont have any network issues.

@shapetheLOLa commented on GitHub (Apr 22, 2025): yea, still having the same. I stopped using the device unfortunately due to this bug. I have cat 6e cables and dont have any network issues.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@ozgith commented on GitHub (Apr 22, 2025):

Same problem continues on my side. I am not using the device any longer as I can’t pass the user / password login on my server.

@ozgith commented on GitHub (Apr 22, 2025): Same problem continues on my side. I am not using the device any longer as I can’t pass the user / password login on my server.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@nblomquist commented on GitHub (Apr 22, 2025):

I too am having this issue. I just got my delivery, 5 devices and the first thing I experience is this bug.

This makes the devices unusable.

EDIT2: The JetKVM seems to work just fine connecting locally, but using the cloud based connection seems to cause this issue.

@nblomquist commented on GitHub (Apr 22, 2025): I too am having this issue. I just got my delivery, 5 devices and the first thing I experience is this bug. This makes the devices unusable. EDIT2: The JetKVM seems to work just fine connecting locally, but using the cloud based connection seems to cause this issue.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@wblondel commented on GitHub (May 3, 2025):

I have the same problem. It happens when connecting locally and via the cloud.

Disabling the mouse solves the issue. But then I have no mouse 😁

@wblondel commented on GitHub (May 3, 2025): I have the same problem. It happens when connecting locally and via the cloud. Disabling the mouse solves the issue. But then I have no mouse 😁

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@kbumsik commented on GitHub (May 5, 2025):

I found that this is especially the problem of JetKVM. JetKVM, among other remote apps, alone is very sensitive to latency spikes: like avg 3ms ping but 300ms at a time.

I mean, 300ms latency itself is not that high to call it a "spike".

JetKVM extremely eager to repeat keypresses when there is a latency spike. This is especially annoying when the problem happens while I press Backword or Space key it really is easy to mess up.

Can we just have an option to disable "Long-press" keys? This will remove repeated inputs for high latency spikes.

@kbumsik commented on GitHub (May 5, 2025): I found that this is especially the problem of JetKVM. JetKVM, among other remote apps, alone is very sensitive to latency spikes: like avg 3ms ping but 300ms at a time. I mean, 300ms latency itself is not that high to call it a "spike". JetKVM extremely eager to repeat keypresses when there is a latency spike. This is especially annoying when the problem happens while I press Backword or Space key it really is easy to mess up. Can we just have an option to disable "Long-press" keys? This will remove repeated inputs for high latency spikes.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@adrianmeraz commented on GitHub (Jun 27, 2025):

This is still an issue, I have the problem daily.

@adrianmeraz commented on GitHub (Jun 27, 2025): This is still an issue, I have the problem daily.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@ozgith commented on GitHub (Jun 27, 2025):

Unfortunately same problem here, I test this after each firmware update with the hope that it may be fixed, but no solution so far.

@ozgith commented on GitHub (Jun 27, 2025): Unfortunately same problem here, I test this after each firmware update with the hope that it may be fixed, but no solution so far.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@pauloon commented on GitHub (Jul 1, 2025):

I still have this same issue, and it is happening more frequently in the latest releases...... Very annoying.
I'm connected through ethernet, and my impression is that if connection has a little bit more of delay due to high traffic on the network, the problem starts to happen.

@pauloon commented on GitHub (Jul 1, 2025): I still have this same issue, and it is happening more frequently in the latest releases...... Very annoying. I'm connected through ethernet, and my impression is that if connection has a little bit more of delay due to high traffic on the network, the problem starts to happen.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@IanSeyler commented on GitHub (Jul 8, 2025):

Issue still present in App 0.4.6 / System 0.2.5

It will even occur when pasting text via the "Paste text" button.

@IanSeyler commented on GitHub (Jul 8, 2025): Issue still present in App 0.4.6 / System 0.2.5 It will even occur when pasting text via the "Paste text" button.

deekerman commented 2026-02-20 08:20:29 -05:00

Author

Owner

Copy link

@nutterbg commented on GitHub (Jul 14, 2025):

I still have this same issue, and it is happening more frequently in the latest releases...... Very annoying. I'm connected through ethernet, and my impression is that if connection has a little bit more of delay due to high traffic on the network, the problem starts to happen.

Can definitely confirm latency is a factor! If I'm remoting in directly via browser, it happens occasionally (mostly when I type fast), but when I add a layer of remoting into the machine that runs the JetKVM browser, it happens distinctly more often to the point it's almost impossible to type.

@nutterbg commented on GitHub (Jul 14, 2025): > I still have this same issue, and it is happening more frequently in the latest releases...... Very annoying. I'm connected through ethernet, and my impression is that if connection has a little bit more of delay due to high traffic on the network, the problem starts to happen. Can definitely confirm latency is a factor! If I'm remoting in directly via browser, it happens occasionally (mostly when I type fast), but when I add a layer of remoting into the machine that runs the JetKVM browser, it happens distinctly more often to the point it's almost impossible to type.

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@nttvuong commented on GitHub (Jul 17, 2025):

with latest software, I encounter this keyboard repeating issue. I am using Mac with Edge.

@nttvuong commented on GitHub (Jul 17, 2025): with latest software, I encounter this keyboard repeating issue. I am using Mac with Edge.

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@Hamtaro25565 commented on GitHub (Jul 22, 2025):

I am running the latest firmware and latest patches on my end devices. Tried multiple browsers (Chromium and Firefox), and find this happens often when typing at speed.

Everything is on Ethernet and I am facing this issue.

@Hamtaro25565 commented on GitHub (Jul 22, 2025): I am running the latest firmware and latest patches on my end devices. Tried multiple browsers (Chromium and Firefox), and find this happens often when typing at speed. Everything is on Ethernet and I am facing this issue.

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@c-s-alex commented on GitHub (Jul 24, 2025):

I got multiple devices and i have this issue daily, it was the only reason i got the kvm and the best feature has this awful bug that makes it unusable.

@c-s-alex commented on GitHub (Jul 24, 2025): I got multiple devices and i have this issue daily, it was the only reason i got the kvm and the best feature has this awful bug that makes it unusable.

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@Plungestep commented on GitHub (Jul 26, 2025):

I also have this issue. The keyboard errors (such as no capital letters or symbols) make this very frustrating to use. Otherwise it is a great product and I would recommend this to everyone! I'm using POP!_OS and an external Logitech keyboard.

@Plungestep commented on GitHub (Jul 26, 2025): I also have this issue. The keyboard errors (such as no capital letters or symbols) make this very frustrating to use. Otherwise it is a great product and I would recommend this to everyone! I'm using POP!_OS and an external Logitech keyboard.

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@ruudboon commented on GitHub (Aug 3, 2025):

Same same

@ruudboon commented on GitHub (Aug 3, 2025): Same same

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@nigelmcdonald commented on GitHub (Aug 8, 2025):

Yeah same issue since day one, it happens in almost every single sentence and I am running on a local cat6 network in the same switch so latency shouldn't be an issue, also I use a wired keyboard so no silliness there. Its basically unusable for anything but monitoring visually

@nigelmcdonald commented on GitHub (Aug 8, 2025): Yeah same issue since day one, it happens in almost every single sentence and I am running on a local cat6 network in the same switch so latency shouldn't be an issue, also I use a wired keyboard so no silliness there. Its basically unusable for anything but monitoring visually

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@IanSeyler commented on GitHub (Aug 15, 2025):

I've switched over to a PiKVM until this gets resolved. Typing via the JetKVM is a terribly frustrating experience. The PiKVM is working fine on the exact same system.. even while connecting to it via Wifi.

@IanSeyler commented on GitHub (Aug 15, 2025): I've switched over to a PiKVM until this gets resolved. Typing via the JetKVM is a terribly frustrating experience. The PiKVM is working fine on the exact same system.. even while connecting to it via Wifi.

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@c-s-alex commented on GitHub (Aug 15, 2025):

I've switched over to a PiKVM until this gets resolved. Typing via the JetKVM is a terribly frustrating experience. The PiKVM is working fine on the exact same system.. even while connecting to it via Wifi.

I will need to switch to something else soon to, it's to disappointing that it's taking so long to fix this core feature

@c-s-alex commented on GitHub (Aug 15, 2025): > I've switched over to a PiKVM until this gets resolved. Typing via the JetKVM is a terribly frustrating experience. The PiKVM is working fine on the exact same system.. even while connecting to it via Wifi. I will need to switch to something else soon to, it's to disappointing that it's taking so long to fix this core feature

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@vitaminmoo commented on GitHub (Aug 18, 2025):

From a diagnostic point of view the likely best path is to first determine if the issue is

1. Between the browser and the JS (keyboard state recognition)
2. Between the JS and the jetkvm (network - unlikely given this happens on low latency/jitter connections)
3. Between the jetkvm and the target system (USB)
4. At the boundary between 1 and 3, but logically (e.g. the translation of 1 to 3 is logically broken somehow)

Note that while it's easy to think of USB keyboard communication as key presses, it's actually a series of report messages that indicate simultaneously which modifiers are active, and which non-modifier keys are actively pressed (in order of being pressed) - this page has a bunch of details. I'm assuming without looking that jetkvm is using boot protocol.

Very likely it's some issue with rollover (key presses overlapping) which happens at higher typing speeds. It's easy to have state issues if this is being emulated from a higher level JS method for getting typed text.

@vitaminmoo commented on GitHub (Aug 18, 2025): From a diagnostic point of view the likely best path is to first determine if the issue is 1. Between the browser and the JS (keyboard state recognition) 2. Between the JS and the jetkvm (network - unlikely given this happens on low latency/jitter connections) 3. Between the jetkvm and the target system (USB) 4. At the boundary between 1 and 3, but logically (e.g. the translation of 1 to 3 is logically broken somehow) Note that while it's easy to think of USB keyboard communication as key presses, it's actually a series of report messages that indicate simultaneously which modifiers are active, and which non-modifier keys are actively pressed (in order of being pressed) - [this page](https://wiki.osdev.org/USB_Human_Interface_Devices) has a bunch of details. I'm assuming without looking that jetkvm is using boot protocol. Very likely it's some issue with rollover (key presses overlapping) which happens at higher typing speeds. It's easy to have state issues if this is being emulated from a higher level JS method for getting typed text.

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@vitaminmoo commented on GitHub (Aug 18, 2025):

A quick experiment using wev on a wayland-based target system to monitor raw-ish events:

[14:     wl_keyboard] key: serial: 4162; time: 294633479; key: 38; state: 1 (pressed)
                      sym: a            (97), utf8: 'a'
[14:     wl_keyboard] key: serial: 4163; time: 294633494; key: 39; state: 1 (pressed)
                      sym: s            (115), utf8: 's'
[14:     wl_keyboard] key: serial: 4164; time: 294633513; key: 40; state: 1 (pressed)
                      sym: d            (100), utf8: 'd'
[14:     wl_keyboard] key: serial: 4165; time: 294633555; key: 41; state: 1 (pressed)
                      sym: f            (102), utf8: 'f'
[14:     wl_keyboard] key: serial: 4166; time: 294636506; key: 39; state: 0 (released)
                      sym: s            (115), utf8: ''
[14:     wl_keyboard] key: serial: 4167; time: 294636506; key: 40; state: 0 (released)
                      sym: d            (100), utf8: ''
[14:     wl_keyboard] key: serial: 4168; time: 294636508; key: 40; state: 1 (pressed)
                      sym: d            (100), utf8: 'd'
[14:     wl_keyboard] key: serial: 4169; time: 294636511; key: 40; state: 0 (released)
                      sym: d            (100), utf8: ''
[14:     wl_keyboard] key: serial: 4170; time: 294636511; key: 41; state: 0 (released)
                      sym: f            (102), utf8: ''
[14:     wl_keyboard] key: serial: 4171; time: 294636516; key: 38; state: 0 (released)
                      sym: a            (97), utf8: ''

This is the output of pressing and holding abcd in that order, then simultaneously releasing all of them. Note the extra d press and release. This appears to happen pretty reliably.

I can also get extra key presses if I simultaneously press two+ keys at the same time - Up to 6 keys should be able to be pressed or released simultaneously or in very rapid succession (again assuming boot protocol is being used)

So yeah, easy reproduction on my end:

1. Press three keys at the same time
2. Release all three keys at the same time

@vitaminmoo commented on GitHub (Aug 18, 2025): A quick experiment using `wev` on a wayland-based target system to monitor raw-ish events: ``` [14: wl_keyboard] key: serial: 4162; time: 294633479; key: 38; state: 1 (pressed) sym: a (97), utf8: 'a' [14: wl_keyboard] key: serial: 4163; time: 294633494; key: 39; state: 1 (pressed) sym: s (115), utf8: 's' [14: wl_keyboard] key: serial: 4164; time: 294633513; key: 40; state: 1 (pressed) sym: d (100), utf8: 'd' [14: wl_keyboard] key: serial: 4165; time: 294633555; key: 41; state: 1 (pressed) sym: f (102), utf8: 'f' [14: wl_keyboard] key: serial: 4166; time: 294636506; key: 39; state: 0 (released) sym: s (115), utf8: '' [14: wl_keyboard] key: serial: 4167; time: 294636506; key: 40; state: 0 (released) sym: d (100), utf8: '' [14: wl_keyboard] key: serial: 4168; time: 294636508; key: 40; state: 1 (pressed) sym: d (100), utf8: 'd' [14: wl_keyboard] key: serial: 4169; time: 294636511; key: 40; state: 0 (released) sym: d (100), utf8: '' [14: wl_keyboard] key: serial: 4170; time: 294636511; key: 41; state: 0 (released) sym: f (102), utf8: '' [14: wl_keyboard] key: serial: 4171; time: 294636516; key: 38; state: 0 (released) sym: a (97), utf8: '' ``` This is the output of pressing and holding `abcd` in that order, then simultaneously releasing all of them. Note the extra `d` press and release. This appears to happen pretty reliably. I can also get extra key presses if I simultaneously press two+ keys at the same time - Up to 6 keys should be able to be pressed or released simultaneously or in very rapid succession (again assuming boot protocol is being used) So yeah, easy reproduction on my end: 1. Press three keys at the same time 2. Release all three keys at the same time

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@rmschooley commented on GitHub (Aug 18, 2025):

If you have not already seen some of the previous debug on this issue, you may be interested to read the following post and others in the same thread:

https://github.com/jetkvm/kvm/issues/325#issuecomment-2900629915

At some point, I believe someone stated that these messages were being passed across the network via UDP (as opposed to TCP). If this were the case, I believe this could explain why these messages could be getting out-of-order. I do not recall any of the main developers confirm that these message are being sent via UDP or if there was any way to force them in order (possibly via TCP).

@rmschooley commented on GitHub (Aug 18, 2025): If you have not already seen some of the previous debug on this issue, you may be interested to read the following post and others in the same thread: https://github.com/jetkvm/kvm/issues/325#issuecomment-2900629915 At some point, I believe someone stated that these messages were being passed across the network via UDP (as opposed to TCP). If this were the case, I believe this could explain why these messages could be getting out-of-order. I do not recall any of the main developers confirm that these message are being sent via UDP or if there was any way to force them in order (possibly via TCP).

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@alexballas commented on GitHub (Aug 22, 2025):

Fix available in #325

@alexballas commented on GitHub (Aug 22, 2025): Fix available in #325

deekerman commented 2026-02-20 08:20:30 -05:00

Author

Owner

Copy link

@adamshiervani commented on GitHub (Sep 18, 2025):

Hey folks,

Over the past couple of weeks we’ve been working through a number of keyboard-related issues. We’ve now fixed enough of them to cut a dev channel release and start gathering feedback.

Prefer stability? Stay on the main update channel and wait until these fixes are rolled out there.
Comfortable experimenting? Switch to the dev channel and update your device to 0.4.8-dev202509181802. For testing, please access the device through the local IP, not JetKVM Cloud. The cloud UI isn't updated to the dev channel, so it will fall back to the old keyboard engine.

We’d love to hear your feedback!

To keep the conversation in one place, I’m closing this issue in favor of #325. Please post any questions or feedback in that thread instead.

@adamshiervani commented on GitHub (Sep 18, 2025): > Hey folks, > > Over the past couple of weeks we’ve been working through a number of keyboard-related issues. We’ve now fixed enough of them to cut a dev channel release and start gathering feedback. > > Prefer stability? Stay on the main update channel and wait until these fixes are rolled out there. > Comfortable experimenting? Switch to the dev channel and update your device to 0.4.8-dev202509181802. For testing, please access the device through the local IP, not JetKVM Cloud. The cloud UI isn't updated to the dev channel, so it will fall back to the old keyboard engine. > > We’d love to hear your feedback! To keep the conversation in one place, I’m closing this issue in favor of #325. Please post any questions or feedback in that thread instead.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

dev

dependabot/npm_and_yarn/ui/vitejs/plugin-react-swc-4.2.3

dependabot/npm_and_yarn/ui/vite-tsconfig-paths-6.1.1

dependabot/npm_and_yarn/ui/framer-motion-12.34.3

dependabot/npm_and_yarn/ui/tailwind-merge-3.5.0

dependabot/npm_and_yarn/ui/multi-d88693a43a

dependabot/go_modules/github.com/pion/webrtc/v4-4.2.9

dependabot/npm_and_yarn/ui/inlang/cli-3.1.6

dependabot/npm_and_yarn/ui/eslint-plugin-react-refresh-0.5.2

dependabot/go_modules/golang.org/x/sys-0.41.0

dependabot/go_modules/golang.org/x/crypto-0.48.0

dependabot/npm_and_yarn/ui/zustand-5.0.11

dependabot/go_modules/github.com/prometheus/procfs-0.20.1

dependabot/npm_and_yarn/ui/inlang/sdk-2.7.0

dependabot/go_modules/github.com/gin-gonic/gin-1.12.0

dependabot/go_modules/golang.org/x/net-0.51.0

dependabot/github_actions/actions/upload-artifact-7

dependabot/npm_and_yarn/ui/npm_and_yarn-e66adb831b

feat/signed-releases

dependabot/go_modules/github.com/prometheus/common-0.67.5

fix/ipv6-readiness

fix/failsafe-tolerance

fix/failscafe-tolerance

debug/native-logs

fix/retry-sleep-mode-check

copilot/add-copilot-instructions-file

chore/es-lint-redux

fix/deploy-cloud-app

release-cloud-app/0.4.9

release-cloud-app/0.4.8

release-cloud-app/0.4.5

release-cloud-app/0.4.4

release-cloud-app/0.4.3

release-cloud-app/0.4.2

release-cloud-app/0.4.1

release-cloud-app/0.4.0

release-cloud-app/0.3.9

release-cloud-app/0.3.8

fix/prevent-video-restart-loop

fix/en-as-default

backports/ota-und-cgo

e2e-tests

release/049

feat/audio-support-metrics

fix/usb-gadget-init-rebind

feat/lldp

feat/usb-reset

feat/audio-support

fix/hdmi-mutex

main

feat/auto-reload-fe

feat/jsonrpc-typings

feat/ocr

chore/show-codec

chore/golangci-lint-additional

refactor/jsonrpc-kbd

misc/0.4.6-with-old-deps

feat/static-ip-ui

cursor/refactor-uselocation-to-prevent-re-renders-f026

cursor/remove-uselocation-from-devices-id-tsx-7751

chore/eslint-prettier-setup

feat/tls-config

feat/metrics-optin

feat/tls

release/0.5.4-dev202602080922

release/0.5.3

release/0.5.3-dev202602061404

release/0.5.3-dev202601281951

release/0.5.2-dev202601071426

release/0.5.2

release/0.5.2-dev202601070105

release/0.5.2-dev202601070032

release/0.5.2-dev202601061215

release/0.5.2-dev202601051816

release/0.5.2-dev202512291946

release/0.5.1-dev202512211114

release/0.5.1

release/0.5.1-dev202512181840

release/0.5.1-dev202512181609

release/0.5.1-dev202512181144

release/0.5.0-dev202512051510

release/0.5.0

0.5.0-dev202511271013

0.5.0-dev202511271020

release/0.5.0-dev202511211223

release/0.5.0-dev20251120

release/0.4.9

release/0.4.8

release/0.4.7

challenge-base

release/0.4.6

release/0.4.5

release/0.4.5-rc2

release/0.4.5-rc1

release/0.4.4

release/0.4.3

release/0.4.2

release/0.4.1

release/0.4.0

release/0.3.9

release/0.3.8

Labels

Clear labels   

component/keyboard-layout

  

component: cloud

  

component: device screen

  

component: extensions

  

component: hid/keyboard

  

component: hid/mouse

  

component: network

  

component: timesync

  

component: ui

  

component: updater

  

component: usb

  

component: usb/hid

  

component: usb/storage

  

component: video

  

component: webrtc

  

component: webserver

  

need-more-details

  

status: working-in-progress

  

wontfix

No labels

component/keyboard-layout

component: cloud

component: device screen

component: extensions

component: hid/keyboard

component: hid/mouse

component: network

component: timesync

component: ui

component: updater

component: usb

component: usb/hid

component: usb/storage

component: video

component: webrtc

component: webserver

need-more-details

status: working-in-progress

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/kvm#113

No description provided.