[ 
https://issues.apache.org/jira/browse/GUACAMOLE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066798#comment-17066798
 ] 

Mike Jumper commented on GUACAMOLE-946:
---------------------------------------

When you connect to the console of a VM using the VNC server provided by your 
hypervisor, that hypervisor must translate received key events from the 
standard value used by VNC which represents key identity (an X11 keysym) to the 
hardware value used by the guest OS (a scancode), the latter really dealing 
only with where the key is located rather than the identity of the key. You 
need to either (1) configure the VM within your virtualization software to 
specify the keyboard layout that will be used within the VM, such that 
hypervisor knows how to translate received keysyms to the needed scancodes, or 
(2) deploy a VNC server within the VM and remain independent of all this.

Some VNC servers and clients support an extension to the VNC protocol which 
allows scancodes to be sent, which is likely why you are able to type at all 
using other VNC clients despite the hypervisor not performing the needed 
translation. There is an issue open for adding this (GUACAMOLE-609), however 
there is debate about whether it really makes sense to add that support given 
Guacamole's goals of client-side keyboard layout independence and seamlessness.

With the underlying issue here being either configuration (in which case there 
is no issue on our end) or support for the QEMU VNC extension implementing 
scancodes (GUACAMOLE-609), I will close this as a duplicate of the latter.

> Russian layout in VNC to Linux
> ------------------------------
>
>                 Key: GUACAMOLE-946
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-946
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole, VNC
>    Affects Versions: 1.0.0
>         Environment: 3.10.0-957.12.2.el7.x86_64 guacamole host, virtualized 
> in vmware
>            Reporter: Vasilii Kuznetcov
>            Priority: Minor
>              Labels: bug, input, language, vnc
>
> Hello, dear support team!
> What was expected:
> Connecting to Linux host via VNC from guacamole, changing the language to 
> Russian (just to be sure that was made in the remote system and in the system 
> accessing to guacamole), trying to type some text and get all the 
> letters/symbols that I pressed on the text editor/console.
> What went wrong: some keys do not type any sign. 
> Diving deep: 
> Tested on different OS (windows 8.1 and 10 and CentOS 7) from different 
> browsers (Google Chrome and Mozilla firefox) on guacamole 1.0 and staging-1.1 
> (build of May 2019). As VNC hosts were used RedHat 7 and CentOS 8. Of course, 
> it was tested with VNC client (tigervnc) to test if this problems exist on 
> server side and there were no problem. 
> What is interesting that it's always 7 keys that are not working in the lower 
> case (In upper it is just one key). That is very interesting becasue in 
> cyrillic alphabet 33 letters and in english 26 and 7 makes the difference 
> between this numbers. The missing letters differs if the different layout of 
> russian were chosen so there can be an assumption that the problem is 
> something there. xev shows no key press when the missing letters are pressed.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to