@bmullan
some x2go troubleshooting steps:
Could you run the following four tests on the terminal of both the affected and the unaffected machine and >compare the output for each test between affected and unaffected?
ssh non-root-userID@ip-of-x2goserver
This has been done for every container attempt and has always ‘worked’.
See if the connection works and if you see a banner message. Make a
copy of the banner message if there is one, so you can compare it.
ssh root@ip-of-x2goserver
This requires ‘root’ to have a password which by definition, in lxd, it doesn’t have - - - so was unable to complete for any one of the 3 instances.
See if the connection works and if you see a banner message. Make acopy of the banner message if there >is one, so you can compare it.
ssh -X non-root-user@ip-of-x2goserver
type “xterm” after you see the shell prompt, see if XTerm comes up and there are no error messages on >the console. NOTE: the “-X” tells SSH to redirect gui on the x2goserver back to the client
The results for this were interesting - - with 3 different results - - - perhaps these results will assist in the troubleshooting.
#1
root@debianbase:/var/log/lightdm# ssh -X memyself@192.168.1.111
memyself@192.168.1.111’s password:
Linux debian-sid-gui 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Jun 2 15:11:59 2018 from 192.168.1.67
/usr/bin/xauth: timeout in locking authority file /home/memyself/.Xauthority
$ xterm
X11 connection rejected because of wrong authentication.
xterm: Xt error: Can’t open display: localhost:10.0
$ exit
#2
root@debianbase:/var/log/lightdm# ssh -X memyself@192.168.1.76
The authenticity of host ‘192.168.1.76 (192.168.1.76)’ can’t be established.
ECDSA key fingerprint is SHA256:ipneCxXo3mmUyw/iGjC3snPlALQIa+akyvszGTDBBqs.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘192.168.1.76’ (ECDSA) to the list of known hosts.
memyself@192.168.1.76’s password:
Linux my-debian-sid-gui 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed May 30 13:26:37 2018 from 192.168.1.67
/usr/bin/xauth: timeout in locking authority file /home/memyself/.Xauthority
$ xterm
X11 connection rejected because of wrong authentication.
xterm: Xt error: Can’t open display: localhost:10.0
$ exit
These first 2 instances seem to have similar difficulties.
#3
root@debianbase:/var/log/lightdm# ssh -X memyself@192.168.1.197
Password: root@debianbase:/var/log/lightdm# ssh -X darald@192.168.1.197
Password:
Linux my-debian-sid-gui2 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
root@debianbase:/var/log/lightdm# ssh -X memyself@192.168.1.197
Password:
Linux my-debian-sid-gui2 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64
The programs included with the Debian GNU/Linux system are free software;root@debianbase:/var/log/lightdm# ssh -X memyself@192.168.1.197
Password:
Linux my-debian-sid-gui2 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jun 1 07:45:51 2018 from 192.168.1.131
/usr/bin/xauth: timeout in locking authority file /home/memyself/.Xauthority
$ xterm
-sh: 1: xterm: not found
root@debianbase:/var/log/lightdm# ssh -X memyself@192.168.1.197
Password:
Linux my-debian-sid-gui2 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jun 1 07:45:51 2018 from 192.168.1.131
/usr/bin/xauth: timeout in locking authority file /home/memyself/.Xauthority
$ xterm
-sh: 1: xterm: not found
Note that just ‘password’ is asked for - - - there is no mention of the ‘userID’
ssh -X root@ip-of-x2goserver
type “xterm” after you see the shell prompt, see if XTerm comes up and there are no error messages on >the console
If you don’t see the Xterm gui window (from the x2goserver) presented to you then you have something >mis-configured on the x2goserver like no desktop installed, no .xauthority file etc.
The first and third instances lxde was installed (for desktop) and with the 2nd the instructions which used Mate was followed for a desktop. Neither option seemed to change results.
It seems to be likely that what is missing is an .xauthority file.
Trying to figure out where the issue is or what is causing the problem i check inside on of my containers:
$ lxc exec my-debian-sid-gui bash
root@my-debian-sid-qui:~# xauth
xauth: file /root/.Xauthority does not exist
Using authority file /root/.Xauthority
xauth>
whereupon I exited.
So - - - it would seem that this is not purely a x2go matter. It would seem that the lxd container function somehow, perhaps, impedes the ‘system’ from having an .Xauthority file.
How do I create one?
I assume it would read /root/.Xauthority for a location.
Please advise.