On Thu, Apr 9, 2015 at 6:42 PM, Christoph Schmidt-Hieber <christsc@gmx.de> wrote:
On Fri, Apr 10, 2015 at 12:13:10AM +0200, Mihai Moldovan wrote:
On 10.04.2015 12:10 AM, Michael DePaulo wrote:
What is your default shell on the server? I have seen various x2go problems (but not this exact problem) when it was set to /bin/tcsh (or a /bin/csh symlink to /bin/tcsh). I suspect that the actual legacy /bin/csh binary would behave even worse with x2go.
We've figured the problem out privately. It was caused by a "exec bash" statement at the end of ~/.profile for one user. Didn't take a look at the other user, but I suspect the same thing there.
I can confirm that removing "exec bash" from .profile solved the problem for the other user as well.
Thanks a lot to Mihai for his extraordinarily fast and efficient help.
Good job Mihai.
This brings up an issue with our documentation though. We should document (probably on our wiki) that a user's .bashrc / .profile / .bash_profile file can interfere with X2Go. Perhaps we should update the error message in x2goclient also.
-Mike#2