noVNC - Arrow Keys misinterpreted when connected via XRDP/x2go

[Fairzweifelt]

Hey there!

This is my PVE:

proxmox-ve: 8.3.0 (running kernel: 6.8.12-9-pve)
pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8: 6.8.12-9
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph: 19.2.1-pve2
ceph-fuse: 19.2.1-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve1
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.3.0
libpve-guest-common-perl: 5.1.7
libpve-http-server-perl: 5.2.0
libpve-network-perl: 0.10.1
libpve-rs-perl: 0.9.2
libpve-storage-perl: 8.3.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.3.6-1
proxmox-backup-file-restore: 3.3.6-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.7
pve-cluster: 8.0.10
pve-container: 5.2.4
pve-docs: 8.3.1
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.15-3
pve-ha-manager: 4.0.6
pve-i18n: 3.4.1
pve-qemu-kvm: 9.2.0-4
pve-xtermjs: 5.5.0-1
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2


I´have a big problem and i wanted to know if there's any workaround:

This is my setup:
Laptop -> XRDP/X2GO -> Workstation-> Firefox/Chromium -> Proxmox -> noVNC (to VM)

All arrow-keys are correctly interpreted until they reach the noVNC-Console in Proxmox (tested with xev on all layers).

But if I start a Debian Live VM in PVE and go to the console and open up a terminal and open "xev" the following keysyms are being transmitted:
UP -> keysym 0xff52, UP
DOWN -> keysym 0xff8d, KP_ENTER
LEFT -> keysym 0xff23, Henkan_Mode
RIGHT -> keysym 0xff22, Mukenkan

~$setxkbmap -query (IN VM!)
rules: evdev
model: pc105
layout: us
options: grp:win_space_toggle,terminate:ctrl_alt_bksp

I've tested Proxmox-Keyobard-Settings under "Datacenter": Default, German, US, UK => same error

The Proxmox-Console is working fine and there are no Errors in LXC-Containers.

So I would guess it has to do with noVNC.

This behavior did not change when it tried the following workarounds on my Workstation:

"setxkbmap -layout de -model pc105 -variant nodeadkeys && firefox" -> same error
chromium -> same error
"LANG=de_DE.UTF-8 firefox" -> same error
"env XKB_DEFAULT_LAYOUT=de firefox" -> same error

"setxkbmap -layout de -model pc105 -variant nodeadkeys" in /etc/xrdp/startwm.sh -> same error

EDIT xrdp_keyboard.ini TO

[default_rdp_layouts]
rdp_layouts=0x00000407

[rdp_layout_0x00000407]
keyboard_type=4
keyboard_subtype=0
keyboard_function_keys=12
layout=de
model=pc105
variant=nodeadkeys
options=

results in same error.

If I plug my Keyboard directly into my Workstation, everything is fine. But this is a little Useless for me because I want to connect to my Workstation from remote-places.

What is left for me to do? I´m pretty desperate.

 

[dcsapak]

If I plug my Keyboard directly into my Workstation, everything is fine. But this is a little Useless for me because I want to connect to my Workstation from remote-places.

but then this seems to be a problem with either x2go (not sending all or wrong key info?) or with the browser wrongly interpreting the keystrokes?