mirror of
https://github.com/jetkvm/kvm.git
synced 2026-03-02 22:58:00 -05:00
Cannot type characters with AltGr key #86
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#86
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 @puigru on GitHub (Jan 30, 2025).
Hello! I just received my JetKVM and I'm pretty pleased with it. However, I'm running into a bit of a bothersome issue with regards to keyboard layout. I can't type certain characters like "@" or "#", which in my Spanish keyboard are entered by pressing AltGr + a number key. I just end up typing the number instead of the special character on the receiving end.
This is especially annoying as you need "@" to type e-mails or mention people in many chat clients, which forces me to resort to using Windows' virtual keyboard. JetKVMs' built-in doesn't cut it because, the layout is wrong there too and I can't seem to find a way to change it.
This is my keyboard layout (characters in blue are typed in combination with AltGr)
JetKVM recognises the key combination of AltGr + 2 (to type @), as such:

@Nevexo commented on GitHub (Jan 30, 2025):
Unfortunately, JetKVM currently only supports the US keymap.
Issue #30 in progress as PR #116
Doesn't really matter what your "controlling" machine has it's keymap set to, the JetKVM tries to type them on it's US keyboard. We'll hopefully be able to test out the wonderful #116 soon and get this resolved.
@dlorch commented on GitHub (May 7, 2025):
Fixed in #399.