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

Mike Jumper commented on GUACAMOLE-1051:
----------------------------------------

I believe this is a duplicate of GUACAMOLE-518:

{quote}
... the issue is that Guacamole's RDP keyboard layout translation system does 
not take the state of Caps Lock into account. The "Caps Lock" key itself is 
correctly handled, but the translation system continues to assume that Shift 
must be pressed to type any uppercase letters, and thus presses Shift 
automatically, effectively reversing Caps Lock.
{quote}

> Bloq Mayus not working with RDP
> -------------------------------
>
>                 Key: GUACAMOLE-1051
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1051
>             Project: Guacamole
>          Issue Type: Bug
>          Components: RDP
>    Affects Versions: 1.2.0
>            Reporter: Edgardo Rodriguez
>            Priority: Trivial
>
> Hi, 
> Building and testing guacamole *staging/1.2.0* from scratch, I found that 
> during a RDP session there is an *issue with Bloq Mayus key*. 
> Pressing it does nothing (going elsewhere like another tab/webpage, shows 
> that mayus key is working). 
> I am unsure if this is a specific restriction due the nature of key being 
> translated or a bug. 
> On the other hand, in a SSH session this is working OK (as desired).
> Pressing Shift+\{Key} does it job ok, as an alternative.
> Also, enabling *Input Method -> Text Input* also restores the intended 
> behaviour.
> Keyboard Layout setting for connection profile was tried empty (as default), 
> latinamerican (mine), and also spanish without any evident impact.
> *Another important fact:* If before logging-in/connecting to an RDP profile 
> you have Bloq Mayus key toggled, everything inside the client will be written 
> in upper-case. Also, it's impossible to disable it.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to