[X2go-dev] BUG: bash login shell required ...

Armin Taschwer armin.taschwer at gmx.at
Thu Mar 4 21:56:25 CET 2010


On Thu, Mar 04, 2010 at 02:36:00PM -0500, John A. Sullivan III wrote:
> On Thu, 2010-03-04 at 12:04 +0000, armin wrote:
> > the session management will fail if you connect to a X2Go server and your
> > default login shell deviates from a BASH.
> > reason: any client tries to export the host environment variable before it
> > starts x2glistsession. export only works for BASH and not e.g. for  tcsh.
> > 
> > if someone is responding to that bug-report i can offer a workaround .. 
> > (i just want to find out if someone is interested in ;)
> <snip>
> We've noticed the same for Ubuntu with its default dash shell.  I'm not
> sure if the export was the only reason or if there were some other
> parsing bash functions that were not working in dash.  Perhaps that's
> another reason why X2Go is focusing its development resources on Lenny.
> Of course, not all Lenny's will be running bash ;) - John

nice .. I got response ;)

At least for a (t)csh I can give you a workaround:
copy following snipset to your ".tcshrc" or ".cshrc" and your session 
management will work again. I'm quite sure similar is possible with other 
shells.

---------------
if ( $?command ) then 
  set is_x2go=`echo $command | grep "x2golistsessions"`
  if ( "x$is_x2go" != "x" ) then
      exec x2golistsessions
  endif
endif
--------------

background: when the x2go client starts to communicate with the server 
(one of) the first command is "export HOSTNAME&&x2golistsessions" which is 
necessary for the session-management.

By sure, this is not a solution in general but for simple setups 
it  will be helpful ..
As a long-term objectiv one should put this into the X2Go todo-list where 
the proper handling of different shells is done within the client - armin






More information about the x2go-dev mailing list