On 02.04.2015 08:26 PM, Michael Stauffer wrote:
On Wed, Apr 1, 2015 at 5:15 PM, Mihai Moldovan <ionic@ionic.de <mailto:ionic@ionic.de>> wrote:
Oh, and that's the good bit -- but very weird bit. "localhost" cannot be resolved on your system. Have you ever edited /etc/hosts? What is its content? Normally, it should include at least the following entries: 127.0.0.1 localhost 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost Which make localhost resolvable.Interesting. My Mac's /etc/hosts is empty. I've added the text you posted above. Great!
Actually, that's pretty weird. Your /etc/hosts file should never be empty on OS X (or actually any other UNIX-based/like operating system.)
May I suggest your system is somewhat hosed and you should investigate what happened? Maybe even reinstall OS X? That's just a personal suggestion and has nothing to do with X2Go, but a missing /etc/hosts file has me concerned about what else might be messed up with that system...
now it's getting further along. I get a new black window opening up with the grey x2go graphic in it, but then I get a sad comput face with the message: "Oh no! Something has gone wrong. A problem has occured and the system can't recover. Please log out and try again. [...]
No need for a debug log here, the issue is clear. You're trying to start up GNOME 3. GNOME 3.10 and later are not compatible, older versions may be, but probably not. For more information, please take a look at:
http://wiki.x2go.org/doku.php/doc:de-compat#compatibility_and_workarounds_de...
Looking at the more detailed x2go server installation page on your site, I then ran this:
yum install x2goserver-xsession
Yes, x2goserver-xsession is recommended/required for full desktop sessions.
I tried x2goclient with a terminal session instead of GNOME and briefly got what looks like an xterm terminal but then it closed. I won't post the debug output here since it's so large.
That's another known bug with new versions of GNOME Terminal. In recent versions, the program is forking into background and X2Go Server can't track that it's running anymore. Instead, it assumes the program terminated and also terminates the session.
We have a workaround for this, but I would rather like to rewrite the affected server script to fix stuff like this in a sane way.
However, take a look at yet another feature of X2Go Client (et al): published applications.
http://wiki.x2go.org/doku.php/wiki:advanced:published-applications
In that mode, you will be able to start GNOME Terminal and it won't quit on you right after starting.
[...] But running gnome-session from the command line over an ssh session gives the same sad computer error page I describe above. Should it work to do that?
About the same issue there: newer GNOME versions require a (newer) GLX extension. I guess that doesn't work at all via ssh -X and nx-libs's GLX extension is too old. That's a side-issue of the stale NX technology we're using. Work is done on improving this situation, but it's not trivial and requires a lot of work, so don't hold your breath for GNOME
= 3.10 or KDE >= 5 support any time soon, sorry...
Mihai