[
https://issues.apache.org/jira/browse/GUACAMOLE-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989960#comment-16989960
]
Keith Johnson commented on GUACAMOLE-609:
-----------------------------------------
[~mjumper] It doesn't appear to be strictly required that libvncclient support
this extension out of the box, as it's possible to implement support for custom
messages/encodings as a client application using libvncclient. I've made a
proof of concept of the changes required to support the qemu extended key
message in the guacd server here:
[https://github.com/rainforestapp/guacamole-server/pull/1/commits/9b03aaf6339442d6e8346719a846d5375858d4ef]
The changes extend the `key` message to take a third argument containing the
scancode. I have not tested it against non-qemu vnc servers yet. Is this an
approach you'd consider merging upstream?
> 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)
