Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Broken Cyrillic encoding at ssh connection

  1. #1
    Join Date
    Mar 2014
    Location
    Dnepropetrovsk
    Posts
    105

    Default Broken Cyrillic encoding at ssh connection

    Good afternoon!

    I am experiencing this problem since installing openSUSE 42.3. In previous oS versions there were no problems with this.

    At my machine Cyrillic letters are displayed properly. But at remote host, connected through ssh, I obtain such result:
    Code:
    $ ls task/SU2DATA/
    ?????????????????? ??????????
    And the most unpleasant thing is that it multiplies substrings when I try to edit string with Cyrillic text through mcedit or vi.
    This is an initial line (there is Russian phrase "Магнитная масса" between "SU2DATA/" and "/TBCDGT_PHI=0.08m"):

    OUTPUTPATH = ../SU2DATA/�~\агни�~Bна�~O ма�~A�~Aа/TBCDGT_PHI=0.08m/4x14x14x14/b3.02/tw/TeslaK40s-02/
    When I just delete the last "4" in "4x14x14x14" substring, I obtain
    OUTPUTPATH = ../SU2DATA/�~\агни�~Bна�~O ма�~A�~Aа/TBCDGT_PHI=0.08m/4x14x14x1x14x14x14/b3.02/tw/TeslaK40s-02/

    This behavior is the same at the all remote machines I tried. Some of them return the following message at the connection:
    /usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct

    The result of locale command at my machine is
    Code:
    > locale
    LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=ce_RU.UTF-8
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    at the remote machine (with error message...):
    Code:
    > locale
    locale: Cannot set LC_ALL to default locale: No such file or directory
    LANG=en_US.UTF-8
    LC_CTYPE="en_US.UTF-8"
    LC_NUMERIC="en_US.UTF-8"
    LC_TIME=ce_RU.UTF-8
    LC_COLLATE="en_US.UTF-8"
    LC_MONETARY="en_US.UTF-8"
    LC_MESSAGES="en_US.UTF-8"
    LC_PAPER="en_US.UTF-8"
    LC_NAME="en_US.UTF-8"
    LC_ADDRESS="en_US.UTF-8"
    LC_TELEPHONE="en_US.UTF-8"
    LC_MEASUREMENT="en_US.UTF-8"
    LC_IDENTIFICATION="en_US.UTF-8"
    LC_ALL=
    Could anybody help me to fix this, please?

    In Internet I have found some advices to fix this, but they don't work for me. I have tried to add the following lines into ~/.ssh/config file:
    Host *
    SendEnv LC_*
    to add the following line into /etc/ssh/ssh_config:
    SendEnv LANG LC_*
    sa well as
    SendEnv LC_TIME="ce_RU.UTF-8"
    SendEnv LC_ALL="en_US.UTF-8"
    the following lines into /etc/environment:
    LANG="en_US.UTF-8"
    LC_TIME="en_US.UTF-8"
    LC_ALL="en_US.UTF-8"
    Nothing helps.

  2. #2
    Join Date
    Sep 2012
    Posts
    7,090

    Default Re: Broken Cyrillic encoding at ssh connection

    Quote Originally Posted by natasha View Post
    Code:
    > locale
    locale: Cannot set LC_ALL to default locale: No such file or directory
    Please post output of "env | grep -E 'LANG|LC_'" from this system.

  3. #3
    Join Date
    Mar 2014
    Location
    Dnepropetrovsk
    Posts
    105

    Default Re: Broken Cyrillic encoding at ssh connection

    Code:
    > env | grep -E 'LANG|LC_'
    LANG=en_US.UTF-8
    LC_TIME=ce_RU.UTF-8
    

  4. #4
    Join Date
    Sep 2012
    Posts
    7,090

    Default Re: Broken Cyrillic encoding at ssh connection

    Hmm ... looks good. Could you do "strace -f -o /tmp/locale.strace locale" and upload /tmp/locale.strace to http://susepaste.org/?

  5. #5
    Join Date
    Mar 2014
    Location
    Dnepropetrovsk
    Posts
    105

    Default Re: Broken Cyrillic encoding at ssh connection

    This is that information from my machine: http://susepaste.org/57888716

    Should I do this at a remote host?

  6. #6
    Join Date
    Mar 2014
    Location
    Dnepropetrovsk
    Posts
    105

    Default Re: Broken Cyrillic encoding at ssh connection

    And, may be this is important, when I login to remote machine from tty command line, I don't obtain any error messages. The Cyrillic encoding is however broken, but at my tty it is broken independently of ssh (this is not principal for me since I usually don't use tty, I normally use it just in case of managing video drivers).

    And if I go to the remote host from mc through Shell link, the Cyrillic text is displayed properly (Midnight Commander is installed from GitHub).

  7. #7
    Join Date
    Sep 2012
    Posts
    7,090

    Default Re: Broken Cyrillic encoding at ssh connection

    Quote Originally Posted by natasha View Post
    Should I do this at a remote host?
    Yes, that's where it fails, right?

  8. #8
    Join Date
    Mar 2014
    Location
    Dnepropetrovsk
    Posts
    105

    Default Re: Broken Cyrillic encoding at ssh connection

    http://susepaste.org/75847661

    Yes, that's where it fails, right?

    Yes. It fails at all remote hosts.

  9. #9
    Join Date
    Sep 2012
    Posts
    7,090

    Default Re: Broken Cyrillic encoding at ssh connection

    What OS is used on remote hosts? The obvious difference is, that on remote host there is file /usr/lib/locale/locale-archive which is not present on local host. I know that Ubuntu (actually likely Debian) is using this file in preference to "split" locale information.

  10. #10
    Join Date
    Mar 2014
    Location
    Dnepropetrovsk
    Posts
    105

    Default Re: Broken Cyrillic encoding at ssh connection

    That hosts have the following OSs:
    Scientific Linux 6.6 (locale.strace is from there);
    openSUSE 13.1;
    openSUSE 42.1;
    Debian 8 Jessie.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •