Hi Mihai,
On So 28 Jul 2013 05:41:12 CEST Mihai Moldovan wrote:
- On 27.07.2013 09:32 PM, Tom Harris wrote:
I had seen some problems similar to this in the past when the user account used a shell other than bash. In the Ubuntu I was using, the default shell was /bin/sh, which failed. I also saw tickets regarding issues with tcsh.
If this is true, x2go's behavior is completely wrong. It shouldn't rely on something like "default" shell but only use scripts with a correct
hashbang to be sure they get executed whatever the system *expects*, (x)or be using POSIX features only and thus ensure execution in any POSIX compatible
shell (is there any non-POSIX compatible shell?)
X2Go Client used to presume /bin/bash as the server-side user shell.
But that has been fixed (I hope) completely. Now server-side commands
are like ,,sh -c ....''. Same with Python X2Go.
My guess about the reported issue is a broken command call in X2Go
Client somewhere. But for this to detect, I need someone who observes
the issue with X2Go Client (4.0.1.1 or newer, version is important,
not yet released) and posts the debug output (x2goclient --debug).
Thanks+Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...