Am 23.01.19 um 13:10 schrieb rubens.zanatta@grad.ufsc.br:
It's not exactly a blank screen, I took a screenshot of the error with the --debug log besides it: https://drive.google.com/open?id=1cgBI3-ARfW4IDdnJeG-4K_iSAhjXuEoz
I see. So you're not getting any additional screen at all, blank or not, but rather the main client window sort of freezes in place.
I'm trying to log in to LXDE, and when I try XFCE, Published Apps and even Terminal I get the same problem. Also, monitoring the syslog on the X2Go server machine I see no X2Go activity during these attempts. Anywhere else I should look that could help troubleshooting this?
Okay, that does indeed smell like an issue with Kerberos.
Can you do two things for me, please?
First, confirm that a regular SSH login using the same username, client, and server, with Kerberos enabled, works. My (limited) understanding of Kerberos says that you should be using these options for SSH *on the client*:
GSSAPIDelegateCredentials no GSSAPIKeyExchange yes GSSAPIRenewalForcesRekey yes PubkeyAuthentication no
I think you should be able to specify them on the command line like so (all on one line):
ssh -o GSSAPIDelegateCredentials=no -o GSSAPIKeyExchange=yes -o GSSAPIRenewalForcesRekey=yes -o PubkeyAuthentication=no user@server
If you can log in to the server like that, without being prompted for a password, then you have a working Kerberos setup. If not, the problem is with your Kerberos setup rather than with X2Go.
Second, can you create an account on the server that does not need to authenticate via Kerberos, and attempt a regular user/password or SSH Public Keyfile login, to see if that works? If that doesn't work, then your X2Go installation (server, client, or both) is botched somehow, and the issue is independent of Kerberos.
Please report back your results.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243