5

The following error has started appearing for myself and all local users of X2Go when attempting to access a remote Ubuntu workstation:

Connection failed. Your home directory path contains non-ASCII characters. Aborting session startup.

Connecting via terminal / ssh still works fine. What is likely causing this error and how could I fix it?

barnhillec
  • 181

3 Answers3

5

The answer is that X2Go will report this error if the root filesystem is full.

barnhillec
  • 181
0

try this command

iconv -f 'ASCII' -t 'ASCII'  <<< "${HOME}

This can happen if your iconv doesn't work.

iconv: relocation error: iconv: symbol __gconv_open version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

I fixed it by reinstalling libc6 on Ubuntu 18.04

sudo apt-get --reinstall install libc6
schspa
  • 1
0

I fixed this problem by rename the iconv in /usr/local/bin.

The command of @schspa outputs an stderr -bash: /usr/local/bin/iconv: No such file or directory, while the output shall be /home/XXX (gotten from a normal server). The phenomenon reminds me to raise the priority of /usr/bin/iconv (default at a normal server) by renaming / removing /usr/local/bin/iconv.

For further information, I put related lines of x2go's source codes below (reference). As you can see, the wrong output of iconv will raise this ambiguous error...

elif ! echo $HOME | iconv -f ASCII -t ASCII 1>/dev/null 2>/dev/null; then  
- echo "Your home directory path contains non-ASCII characters. Aborting session startup."  
+ msg="Your home directory path contains non-ASCII characters. Aborting session startup."  
+ echo "$msg"  
+ $X2GO_LIB_PATH/x2gosyslog "$0" "error" "$msg"  
exit -5  
fi
Yuankuan Zhang
  • 1