Hello,
I've a weird "bug" on RDM since a week or so. I've put "bug" between quotes because coworkers who use the exact same version and data source as me don't have the issue.
When in an SSH session, some keys are not working, namely "a", "r", "g". When I type them, they aren't inputted inside the console. All other keys work as expected.
If type my command in an external text editor and copy&paste it inside the SSH session, it works without issue.
It happens in all SSH sessions. Only SSH sessions (RDP sessions works well).
I'm pulling my hair trying to understand what could cause this issue. I've not found any settings that may explains this.
Anyone know what may be happening?
I'm on RDM 2025.3.32.0 (update to 2026.1 is planned but a bit complicated because we need to coordinate everyone to update at the same time due to the database schema update).
I run Windows 11 25H2, my keyboard is a french AZERTY layout.
Hello,
Since the issue only occurs on one computer and your coworkers using the same RDM version and data source do not have the issue, this seems more likely to be related to a local configuration or environment-specific setting.
Could you confirm if the other users who tested successfully are also using a French AZERTY keyboard layout?
As a next step, could you please try resetting Remote Desktop Manager to its default local settings by following this article:
https://docs.devolutions.net/rdm/kb/how-to-articles/reset-rdm-to-default-settings/
Please let us know the result after testing this.
Best regards,
Carl Marien
Hello,
My coworkers are using the same keyboard layout.
In my case the issue started about a week ago, there have been no RDM updates nor Windows Update (latest Windows Update was a .NET update installed on 15/04, and RDM still worked as expected afterwards).
I still have the same issue after resetting RDM (by renaming the directory as documented, and reimporting the .rdd file)
Hello,
Thank you for the additional information.
Since your coworkers are using the same keyboard layout, the same RDM version, and the same data source without experiencing the issue, and since resetting the local RDM configuration did not resolve it, I would like to try isolating the problem further.
Could you please test the same SSH sessions from another computer?
This will help us determine whether the behavior is linked to your specific workstation/environment or to something associated with your user/profile.
Please let us know if the issue also occurs on the other computer.
Best regards,
Carl Marien