[
https://issues.apache.org/jira/browse/GUACAMOLE-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429720#comment-15429720
]
Michael Jumper commented on GUACAMOLE-83:
-----------------------------------------
For RDP, this should have been fixed recently with the merge of GUACAMOLE-51.
When you tested this, how recent was your build from git?
{quote}
Apparently the same thing applies to VNC, and is valid only for RDP starting
with Windows 7 / 2012R2.
{quote}
Unfortunately, this is a bug in your VNC server. From the [VNC
specification|https://tools.ietf.org/html/rfc6143]:
{quote}
The "shift state" (i.e., whether either of the Shift keysyms is down) should
only be used as a hint when interpreting a keysym. For example, on a US
keyboard the '#' character is shifted, but on a UK keyboard it is not. A
server with a US keyboard receiving a '#' character from a client with a UK
keyboard will not have been sent any shift presses. In this case, it is likely
that the server will internally need to simulate a shift press on its local
system in order to get a '#' character and not a '3'.
...
Servers should ignore "lock" keysyms such as CapsLock and NumLock where
possible. Instead, they should interpret each character-based keysym according
to its case.
{quote}
VNC servers are required to interpret key events independently of any received
modifier or lock key events, and set modifiers (or locks) as required to cause
the desired effect within the remote desktop session (the same thing
Guacamole's RDP keymap system does due to RDP's dependence on scancodes).
> Numeric keypad not working in RDP
> ---------------------------------
>
> Key: GUACAMOLE-83
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-83
> Project: Guacamole
> Issue Type: Bug
> Affects Versions: 0.9.9, 0.9.10-incubating
> Reporter: J-M Roth
>
> I've experienced this issue myself and found a similar report on the mailing
> list
> (https://sourceforge.net/p/guacamole/discussion/1110834/thread/2ff8d94e/?limit=25).
> Yet I have found no bug report, therefore here it is.
> Fact is that the numeric keypad inside a session is not working. (The +/*-
> keys are ok but the numbers are not.)
> A workaround seems to be to have numlock disabled when starting the session
> and enabling numlock later. In that case, typing numbers using the numeric
> keypad is working. (On the mailing list someone said that would not always
> work.)
> Apparently the same thing applies to VNC, and is valid only for RDP starting
> with Windows 7 / 2012R2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
