[
https://issues.apache.org/jira/browse/GUACAMOLE-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990132#comment-16990132
]
Mike Jumper commented on GUACAMOLE-609:
---------------------------------------
It is definitely worth considering, however I'm hesitant about including
scancodes within the {{key}} instruction. Doing so would be a step backward
from Guacamole's intent to be layout-independent on the client side.
What about using a keysym-to-scancode translation layer similar to the RDP
support? In that case, similar to RDP connections, VNC connections using QEMU
would need to be configured with the keyboard layout of the machine within
QEMU, but things would remain layout-independent on the client side.
> Add support for QEMU extended key events
> ----------------------------------------
>
> Key: GUACAMOLE-609
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-609
> Project: Guacamole
> Issue Type: Improvement
> Components: VNC
> Environment: Parrot VM inside KVM-QEMU
> Reporter: faelis
> Priority: Minor
>
> When guacamole is connected to a VM running inside qemu using the built in
> VNC, my physical azerty keyboard looks like acting as a qwerty keyboard.
> If the layout inside the VM is set to qwerty it works nearly correct.
> If the layout inside the VM is set to azerty it doesn't work (a=q,z=w,
> etc...).
> If I use novnc instead of guacamole, the keyboard works fine.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
