You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting with newly generated linux client to newly installed Leonardo server, from a client with non us keyboard, the keyboard layout ( Italian ) is not properly passed on and remote VNC is configured as US keyboard, resulting in incorrect mapping.
This just happens on Leonardo
Possible relevant differencies could be:
on Leonardo the command localctl returns:
[lcalori0@login02 ~]$ localectl
System Locale: LANG=en_US.UTF-8
VC Keymap: us
X11 Layout: n/a
NOTE: X11 Layout: n/a
While on G100:
[lcalori0@login10 ~]$ localectl
System Locale: LANG=en_US.UTF-8
VC Keymap: us
X11 Layout: us
Also, while on Leonardo the installed turbovnc server version is
TurboVNC Server v3.1.1
on G100 is
TurboVNC Server v2.2.5
It could be that, in case of matching or similar client and server version of TurboVNC the needed mapping between keyword simbols is disabled.
TODO:
install new VNC server on G100 to see if the problem happen there
see if downgrading client VNC version works around the problem
The text was updated successfully, but these errors were encountered:
When connecting with newly generated linux client to newly installed Leonardo server, from a client with non us keyboard, the keyboard layout ( Italian ) is not properly passed on and remote VNC is configured as US keyboard, resulting in incorrect mapping.
This just happens on Leonardo
Possible relevant differencies could be:
on Leonardo the command localctl returns:
[lcalori0@login02 ~]$ localectl
System Locale: LANG=en_US.UTF-8
VC Keymap: us
X11 Layout: n/a
NOTE: X11 Layout: n/a
While on G100:
[lcalori0@login10 ~]$ localectl
System Locale: LANG=en_US.UTF-8
VC Keymap: us
X11 Layout: us
Also, while on Leonardo the installed turbovnc server version is
TurboVNC Server v3.1.1
on G100 is
TurboVNC Server v2.2.5
It could be that, in case of matching or similar client and server version of TurboVNC the needed mapping between keyword simbols is disabled.
TODO:
install new VNC server on G100 to see if the problem happen there
see if downgrading client VNC version works around the problem
The text was updated successfully, but these errors were encountered: