Keyboard shortcuts on VNC and layout on RDP
Hi,
I'm using Remote Desktop Manager on both my Samsung S25U and my Google Pixel phone, and I'm having issues using the keyboard.
When connecting to a Linux VNC server (TigerVNC), when I try to type keys with modifiers like Ctrl-C, Ctrl-X, Ctrl-D it doesn't work, it sends other kind of keys in its place (for example, in a terminal, if I type Ctrl-X, instead it presses Ctrl-Minus which is the shortcut to zoom out). But typing normal keys (without modifier) is fine. I can fix that problem by enabling the "legacy keyboard processing", and now Ctrl shortcuts are working again. But if I enable that option, then connecting to RDP is a problem: the keyboard layout is wrong (QWERTY instead of my usual AZERTY), even after changing the keyboard layout in RDM options. If I switch "legacy keyboard processing" back off, RDP works fine again. So I have to set that option in advance depending on the type of server I'm connecting to ;)
I already tried the "keyboard layout compatibility mode" without success. Tell me what I should try next.
All Comments (7)
Hello,
Thank you for contacting Devolutions Support.
I attempted to reproduce the issue on my end but was unfortunately unable to do so.
Could you please let me know whether you are using an external keyboard when the issue occurs?
Best regards,
Carl Marien
No, I'm using the Samsung keyboard on the S25U and Gboard on the Pixel.
Which issue can't you reproduce, the VNC one or the RDP? Or both?
Hello,
Thank you for your patience.
I’ve initiated an investigation on our end, and I’ll reach out if the QA team requires any additional information to reproduce the issue.
Best regards,
Carl Marien
Hi,
Is there any update on this bug? Did you have the time to test this? Or do you need more information on my part?
Yann
Hello,
I’ve submitted your case to our QA team for investigation. It has been logged internally and is currently under review.
I’ll follow up as soon as we have any updates.
Best regards,
Carl Marien
Hi,
The shortcut issue has been identified, and a fix will be included in our upcoming release. Please ensure that the "Legacy Keyboard Processing" option is disabled.
Regarding the keyboard layout issue, we have tested it thoroughly and determined that the problem is not on our end. When we debug the behavior, the correct key code is sent to the server. For example, pressing the letter "A" sends the correct code (65), but the server misinterprets it as code 81, corresponding to the letter "Q." Unfortunately, this is beyond our control, and there's little we can do to address it.
Best Regards,
Nicolas Dufour
Hello,
A version containing the fix has been released: 2025.2.2.2.
Best regards,
Maxime Brousseau