**
Hi everyone,
I’m running both *guacamole-server* and *guacamole-client* on my own
implementation of Guacamole — I’ve rewritten the frontend in *React*,
following the logic and specs from the original Angular code.
I’m running into a strange issue that seems to happen *only on XRDP
sessions to Linux machines* (I haven’t seen it on Windows).
Basically, it looks like the *Shift key stays “stuck”* in the backend
after some time.
For example:
*
When I press *CTRL+C*, Guacamole sends *CTRL+SHIFT+C* instead (in
NetBeans, this triggers “comment block” instead of copy).
*
*CTRL+S* becomes *CTRL+SHIFT+S* (“Save As”).
I already implemented things like keyboard resets on focus loss, as done
in the official frontend, but the issue still occurs.
Has anyone ever experienced or reported something similar?
Could this be related to XRDP or to how keyboard state synchronization
works between the client and the Guacamole protocol?
Any hints or past discussions would be appreciated.
Thanks in advance,
steph01
