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

Thomas Kobber Panum commented on GUACAMOLE-657:
-----------------------------------------------

I have the exact same issue as Kaspar describe, and my setup is as follows:
 * VirtualBox's RDP Solution (version 5.2.18r124319)
 * Virtual Guests: Two linux systems (one with GNOME and one with XFCE – tried 
also just accessing tty)
 * Guacamole version 0.9.14
 * Browser: Firefox 62, Chromium 69 (running on Linux with just a window 
manager)

When I use an RDP Client (Remmina 1.2.31) performing _Ctrl + Alt + Shift_ 
+*does not*+ make Ctrl become stuck in the virtual guest.

When doing the same thing through Guacamole I see the keyup event (of Ctrl) 
being sent from the web client, but the ctrl is still stuck within the guest. 
The same happens on a Windows client running Chrome 69, but the problem also 
occurs there.

In my use case it sadly creates a lot of frustration for the users, as using 
the clipboard feature simply makes their RDP solution become unusable 
afterwards.

So as mentioned, I believe that the JavaScript client correctly handles the 
reset() correctly, but guacd does not pass it on correct to the RDP connection 
(since the issue does not occur using other RDP clients?)

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

Reply via email to