mirror of
https://github.com/jetkvm/kvm.git
synced 2026-03-02 22:58:00 -05:00
All keyboard input not working (paste, virtual keyboard, physical keyboard) after reboot #241
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/kvm#241
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mgleason2002 on GitHub (May 4, 2025).
App: 0.3.9
System: 0.2.3
Using an Minisforum MS-01 connected with USB C to A cable that came in the box. OS is Proxmox 8.3.5.
After rebooting the machine, JetKVM does not register any inputs from the Paste text box, virtual keyboard or physical keyboard.
Semi-reliable workaround has been to go to Settings > Hardware > Identifiers and select a different keyboard emulation. Sometimes it requires two or three changes to any random identifier, then all keyboard input, paste, etc will start working normally. Works while the system is up and running, has to be redone after reboot every time.
@harrywustl commented on GitHub (May 4, 2025):
Same issue as well, with HP Z240.
@molotch commented on GitHub (May 20, 2025):
Same problem, also running proxmox on a ASUS PN51 nuc. Had problems getting USB to be recognized in the first place, but now it says connected but no keystrokes are getting through to the OS.
@geozeke commented on GitHub (May 22, 2025):
Had the same issue after the
0.4.1update. Just happen to checkSettings > Keyboard, and noticed that my keyboard layout switched from my preferred, toBelgisch Nederlandsfor some reason. Switched it back to my preferred layout, and all is well.@molotch commented on GitHub (May 23, 2025):
Seems to be some rolling updates. I'm still on App: 0.3.9, System: 0.2.4 and update says I'm running the latest version.
I don't even have a Settings > Keyboard setting, only mouse.
Still keyboard presses aren't going through.
@Emeraude998 commented on GitHub (May 28, 2025):
Same issue for me, I'm on App: 0.4.1, System: 0.2.4 and using the KVM to monitor a Proxmox node with a DC extension.
I saw that the language was set to
Belgisch Nederlandstoo, switch it back toFrenchbut the issue persists.I noticed the problem after a power outage.
Rebooting both the KVM and the Proxmox node don't seem to fix the issue.
Also, that setting doesn't seem to be effective as when I press any key on my
AZERTYlayout keyboard, it shows on the bottom left the correspondingQWERTYlayout key...@molotch commented on GitHub (Jun 5, 2025):
Mine started working once I updated to 0.4.1 (you have to enable Dev Channel Updates under Advanced in settings). I use the settings Hardware -> Usb Device -> Classes: Keyboard Only and Identifier JetKVM Default.
@pessimal commented on GitHub (Jun 17, 2025):
Everything was working fine yesterday, today no keyboard inputs of any kind. None of the workarounds posted here have worked so far.
App: 0.4.4
System 0.2.4
Edit: In the end I had to physically change the usb port for things to start working again, not even unbinding and rebinding the old one had any effect
@Crash1602 commented on GitHub (Jul 14, 2025):
Unfortunately, I’m experiencing the same issue.
App: 0.4.6
System: 0.2.5
An Intel NUC i9 13900K and a Dell Optiplex 3000 only sporadically respond to input—regardless of whether I'm using the physical or virtual keyboard. Letters, numbers, and arrow keys don't react. After rebooting the JetKVM, it works briefly, but as soon as the host reboots (e.g., during a BIOS update), the keyboard stops responding again. I had just updated from 0.3.9 to 0.4.6 shortly before. I didn’t notice these issues with version 0.3.9.
The lower bar correctly shows what’s being typed, but nothing reaches the host. I tested it with Edge Chromium and Firefox (my Main-Browser) at a Linux PC and Windows 11 PC.
@j796160836 commented on GitHub (Jul 26, 2025):
Maybe issue #239 is related
@rgl commented on GitHub (Aug 4, 2025):
FWIW, this also happens in a Dell OptiPlex 7060 Micro. After some time, the USB keyboard stops working, and only reconnecting the USB cable makes it works again.
@joelis10 commented on GitHub (Aug 21, 2025):
Happens to me too and can't seem to fix it. First, keyboard went a bit spazzy with sometimes keeping a key held down for longer than I'd pressed it but now it's gone completely.
Edit: fixed by unplugging the JetKVM and plugging it back in but no idea how long it'll stay fixed for
@alexruffell commented on GitHub (Aug 31, 2025):
I have 3 JetKVM units that all stopped accepting keyboard strokes at the same time. All 3 are connected to ProxMox hosts. I got one to work briefly by using incognito mode but that didn't last long.
Image because I can't copy paste the version info for some reason - annoying!
@CrustyB commented on GitHub (Sep 11, 2025):
Same. all keyboard input (including the virtual keyboard) stopped working. MS-01
@mmozzano commented on GitHub (Sep 13, 2025):
Same issue here, looks like I was on the dev firmware branch which downloaded 0.4.7 which seems very unstable. I wasnt able to select options in the gui nor would keyboard input work.
I performed a reflash using DFU mode and its resolved the issue. Instructions are here: https://jetkvm.com/docs/advanced-usage/factory-reset
After the DFU reflash I was on version 0.4.5 and then I performed an update to 0.4.6 which looks like the most recent non dev firmware. I'll be staying away from dev firmwares going forward.
@Crash1602 commented on GitHub (Oct 13, 2025):
I have installed App 0.4.8 and System 0.2.5, and unfortunately the issue still occurs exactly as before :-(
At first all inputs work, then I perform a restart because I want to do a BIOS update using a mounted IMG file, and immediately after this first reboot of the host the keyboard keys no longer respond—for example, I can’t open the boot menu.
@Crash1602 commented on GitHub (Dec 4, 2025):
I'd like to ask if the problem is still being investigated, if a solution is being worked on, or if it's still being monitored? Yesterday I had another instance where the keyboard signals weren't being transmitted to the device :-/
@eddieparker commented on GitHub (Dec 15, 2025):
I was experiencing this too, until I realized that I plugged in the splitter that came with the boxes - it only gave power to the devices, but didn't provide input.
I took out the splitter, and things worked.
I couldn't find any documentation about the splitter anywhere, so I thought it was necessary. If I had to guess, I'd probably want to plug the lightning-bolt symbol to power (i.e., a USB wall wart) and the USB symbol to thePC, my guess being that would provide me with power when the device was shutdown.
Not sure if others are experiencing this for the same reason, but thought I'd mention it.
@Crash1602 commented on GitHub (Dec 17, 2025):
@eddieparker
That’s an interesting hint. I couldn’t test it myself because I don’t have a power injector or PoE, but my colleague is running this setup using a power injector via RJ45 and doesn’t have this problem. So it does seem that the USB-C splitter is causing the issue.
@angelomelonas commented on GitHub (Jan 2, 2026):
I am also experiencing this issue on a Dell OptiPlex 3060 (SFF) running Proxmox. The JetKVM is powered by an external USB adapter, using the splitter cable.
The keyboard sometimes works (after restarting the host), but even after trying all of the suggestions above (excluding the factory reset) I can't get it working consistently.