[
https://issues.apache.org/jira/browse/GUACAMOLE-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681801#comment-16681801
]
Kaspar Hageman commented on GUACAMOLE-657:
------------------------------------------
Right, so if I understand correctly, there are two mechanisms in play here:
# The "Meta" key is not mapped to any RDP key and therefore will never reach
the VM in the first place. Mapping the Windows key to Meta would solve this
issue? Or is this a deliberate design choice?
# The "Ctrl" key release is not send from the browser to Guacamole as a
WebSocket frame (from what I can observe from the Chrome developer) and
therefore will never reach the VM in the first place. I would assume this is a
legitimate bug.
> Unexpected behaviour of modifier keys when opening Guacamole menu
> -----------------------------------------------------------------
>
> Key: GUACAMOLE-657
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-657
> Project: Guacamole
> Issue Type: Bug
> Components: RDP
> Affects Versions: 0.9.14
> Environment: Host: macOS Mojave
> Browser: Chrome 70
> Guest: Kali Linux (VirtualBox 5.2.18)
> Reporter: Kaspar Hageman
> Priority: Major
>
> When opening the Guacamole menu, during an RDP session with a VM, with the
> default key combination (Ctrl + Cmd + Shift), the VM does observe key events
> as expected.
> For instance, when pressing Ctrl + Cmd + Shift (in that order), the following
> key events can be observed (using Chrome's developer tools):
> * Ctrl pressed
> * Cmd pressed
> * Shift released
> * Ctrl released
> * Cmd released
> However, in the VM, the following key events can be observed (using xev):
> * Ctrl pressed
> Has been tested with both version 0.9.14 and the current master branch
> (d4f58f2c0d812b05c392e06438e659902e8121f8)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
