guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Jumper (JIRA)" <>
Subject [jira] [Commented] (GUACAMOLE-51) Keypad not properly mapped in RDP, SSH, and telnet
Date Sun, 14 Aug 2016 21:54:20 GMT


Michael Jumper commented on GUACAMOLE-51:

While testing tracking of lock state, it's worth noting that ChromeOS has a bug where Caps
lock is mapped to F16. From

On ChromeOS, CapsLock arrives as F16 (, and chromeos::EventRewriter converts
F16 to CapsLock (VKEY_CAPITAL), and a fake X11 event is generated to match, mapping VKEY ->
X KeySym -> X keycode. The last step fails, because X has no keycode that maps to XK_Caps_Lock

Annoying, but if anyone ever wonders why Caps is not sent properly on ChromeOS, that's why.
It will still ultimately work, even with RDP, as the key translation system will automatically
press Shift when it receives capital letter keypresses while Shift is known to be released.
As F16 is not currently mapped for RDP, the Caps key event is just dropped.

> Keypad not properly mapped in RDP, SSH, and telnet
> --------------------------------------------------
>                 Key: GUACAMOLE-51
>                 URL:
>             Project: Guacamole
>          Issue Type: Bug
>          Components: RDP, SSH, Telnet
>    Affects Versions: 0.9.8, 0.9.9
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>             Fix For: 0.9.10-incubating
> {panel:bgColor=#FFFFEE}
> *This issue is the coninuation of [GUAC-1460|],
an issue in the JIRA instance used by the Guacamole project prior to its acceptance into the
Apache Incubator.*
> Comments, attachments, related issues, and history from prior to acceptance *have not
been copied* and can be found instead at the original issue.
> {panel}
> Explicit support for the keys of the number pad was added back in 0.9.8 via [GUAC-1314|],
allowing Guacamole to handle those keys distinctly, but the keyboard mappings used by RDP,
SSH, and telnet were not brought up-to-date. This means that the keys no longer have their
expected effect if the browser actually supports distinguishing the number pad from the rest
of the keyboard.
> VNC is unaffected, as no mapping is necessary.

This message was sent by Atlassian JIRA

View raw message