[X2Go-User] Quick little trouble shooting instructions I set up for my users.

[Robert Dinse]

      I see no reason to limit to XFCE, I personally use Mate, but have Gnome,
XFCE, LXDE, LXQT, and KDE all installed on my servers and they all work with
x2go.  With Gnome it is necessary to have gnome-flashback, 
gnome-session-flashback, and gnome-flashback-common for it to work properly, 
else you'll just get a black screen.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
    Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Fri, 19 Apr 2019, Jeff Sadowski wrote:

> Date: Fri, 19 Apr 2019 14:07:41 -0600
> From: Jeff Sadowski <jeff.sadowski at gmail.com>
> To: x2go-user at lists.x2go.org
> Subject: [X2Go-User] Quick little trouble shooting instructions I set up for
>     my users.
> 
> My .bashrc starts like so
>
> if [ "$BASH_EXECUTION_STRING" != "" ]; then return 0; fi
> # do not add items before this line
>
> This helps with sftp and x2go if you have things that interfere with
> x2go or sftp like changing directories or adding paths that might
> interfere or just code block that might interfere.
>
> Always set the session type to XFCE default is KDE(not installed on
> all servers).
> XFCE is a lightweight desktop  allowing more people to connect.
> if XFCE fails to start with
>
> a dbus error you may have a corrupted file in your home directory.
>
> One way to potentially fix this is to login with ssh and move all your
> dot files to a temporary directory like so
>
> mkdir -p ~/dot_files
> mv ~/.[a-zA-Z]* ~/dot_files
> After your dot files are out of the way try starting an x2go session.
>
> If it starts then one of the files was causing the issue.
>
> to move your files back that have not been created by starting x2go
>
> you can try this script I called restore_dot_files.sh
>
> #!/bin/bash
> #script to move back all files that where not recreated by starting xfce
> cd ~/dot_files
> ls -1 .[a-zA-Z]* | while read file;
> do
> if [ ! -e "${HOME}/${file}" ];then
> echo "moving back ${file}"
> mv "$file" ~/
> fi
> done
>
> then try stopping and starting x2go and see if it still fails. If it
> fails then one of the files that is being copied back is causing the
> issue maybe ~/.bashrc I'd make sure you have the lines I have at the
> top of this article the top and bottom sections of my .bashrc and try
> again.
>
> If you are having issues with connecting to previous sessions you may
> need to login from a command line with an ssh client (like putty, or
> mobaxterm) and kill some hung sessions. Login to the server you can
> not connect to. Run:
>
> ps -fu $USER|grep x2goagent
>
> This will display your current x2goagent processes you have running
>
> Ex:
>
> user1::machine1 { ~ }-> ps -fu $USER |grep x2goagent
> user1 22323 1 0 Apr08 ? 00:05:22 x2goagent -nolisten tcp -nolisten tcp
> -dpi 96 -D -auth /home/user1/.Xauthority -geometry 800x600 -name
> X2GO-user1-53-1554730849_stDXFCE_dp24 :53
>
> In this example if I can no longer connect to my x2go session on
> machine1 I would want to kill this process. So I would run:
>
> kill 22323
> After running that see if there is still a process x2goruncommand by running
>
> ps -fu $USER |grep x2goruncommand
> Ex:
>
> user1::machine1 { ~ }-> ps -fu $USER |grep x2goruncommand
> user1 22383 1 0 Apr08 ? 00:00:00 /bin/bash /usr/bin/x2goruncommand 53
> 22323 user1-53-1554730849_stDXFCE_dp24 52312 xfce4-session nosnd D
>
> you will want to try and kill that process as well in this example I
> would use the following to kill it
>
> kill 22383
> After you kill those two processes you should be able to connect to
> that server again using x2go.
> _______________________________________________
> x2go-user mailing list
> x2go-user at lists.x2go.org
> https://lists.x2go.org/listinfo/x2go-user