SSH default locale linux server is changed to en_US
Hi,
I observe a problem with RDM ssh connections.
It's like RDM redefine the default locale when connecting to a linux server.
For instance if I ssh to myuser on server A, and then execute the command line export, I see :
declare -x LANG="en_US.UTF-8"
if now I log on root with command line, and then su - myuser, now if I execute the export command, I'll see:
declare -x LANG="fr_FR.UTF-8"
which is the correct default locale of the server
I'd like to specify that there is no environment variable 'LANG' in the
'.bash_profile', nor any script that modifies the 'LANG' environment
variable.
Where does RDM redefine the locale ?
Best regards,
Nicolas
All Comments (9)
Hello Nicolas,
Thank you for contacting us on that matter.
This issue seems to be related to the language used.
When using sudo, this issue does not happen.
Could you tell us if your RDM is set in French or English?
If you use it in English, could you change the language to French by File -> Options -> User Interface -> Langage?
Could you provide the verbose logs from the RDM set at Level 2?
https://docs.devolutions.net/kb/remote-desktop-manager/how-to-articles/send-ssh-logs-verbose/
Best regards,
Patrick Ouimet
Hello Patrick,
My RDM is already set in french.
I've set debug level at 2 in the ssh connection and I got the log file I've joined to this conversation.
Thanks for your help,
Nicolas
RDM_ssh.log
Hello Nicolas,
Thank you for this log.
I've sent it to the engineering department.
I'll let you know as soon as I have news from them.
Best regards,
Patrick Ouimet
Thanks a lot for your help!
Hello Nicolas,
Could you enable the option Skip environment variable setup into the entry properties -> General -> Advanced?
Let us know if his issue still occurs after this.
Best regards,
Patrick Ouimet
Hello Patrick,
That solves the problem!
Thank you for your reactivity,
Best regards
Nicolas
Hello Nicolas,
Thank you for this feedback.
I will wait for the engineering department to fix this issue and then post the fix version.
Best regards,
Patrick Ouimet
That's great!
Hello Nicolas,
I wanted to update you on the status of this case. The issue is expected to be resolved in the upcoming version 2023.2.32.0, which should be available soon.
Best regards,
Patrick Ouimet