[jira] [Closed] (GUACAMOLE-946) Russian layout in VNC to Linux

["Mike Jumper (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GUACAMOLE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Jumper closed GUACAMOLE-946.
---------------------------------
    Resolution: Duplicate

> 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)