For what it's worth ksh also works fine.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Sun, 13 Sep 2015, Mihai Moldovan wrote:
Date: Sun, 13 Sep 2015 02:17:55 +0200 From: Mihai Moldovan <ionic@ionic.de> To: Chris <devnullaccount@yahoo.se>, x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Problems with x2go
On 10.09.2015 09:18 AM, Chris wrote:
Issue 1: First I tried "X2Go Client" and that one just keeps crashing on me. I only need to enter the "session preferences" dialog and as soon as I press ok (independent if I change anything or not), the program crashes and Windows tells me "x2goclient.exe has stopped working". Similar crash if I try to start a session. This with X2Go Client v. 4.0.5.0 (Qt - 4.8.6) on Windows 7. I tried an older version 4.0.2.x which did not crash so there seems to be something off with the most recent version. Known issue?
I've heard about crashes when exiting preferences. Looks like I introduced that in 4.0.5.0 while fixing the always inactive edit/delete/create buttons.
Will take a look at it eventually.
Starting a session shouldn't cause a crash, though.
Issue 2: So I installed PyHoCa-GUI instead. That one is stable and mostly works. But when I choose "custom command" as the session, it refuses to run any command with an absolute path and only accepts things in places like /usr/bin/. Perhaps it is some path-issue, but it also does not accept things in /home/myname/bin/, which is in my $PATH from the shell. Note: I'm using zsh as my login shell. Is this a bug or am I not supposed to be able to run things with absolute paths? (note: I have double-checked file permissions and the things I'm pointing to under /home are +rw for everyone). I don't want to have to put my session script in /usr/bin/
X2Go Client (and PyHoca) expect bash as the login shell. While zsh might work because it's bash-compatible enough, there is no way to know what your startup scripts do to make a session start fail.
An absolute path is supported by X2Go Client - but there's a chance PyHoca handles this differently. Generally, it is supported by the server scripts.
Question 1: No matter if I use the "X2Go client" or "PyHoCa-GUI", I don't get the keyboard behavior I would like. Using VNC, it will just map each keypress from Windows and pass those symbols into the server, which is important since I use a custom keyboard definition. That doesn't seem to work with x2go as I get pc104/us both if I tell it to "do not set" or "automatically detect". And if I choose "use custom keyboard", I can only select a "standard" keymap, I have no idea how to tell it to use a custom keymap. Is it so that x2go can't handle user-defined keymaps and only handles standard keymaps?
This behavior unfortunately depends on the OS used. On Linux, which already uses the X11 system, settings can be mostly trouble-free passed-through. Custom keymaps could be a problem there.
On OS X, the whole key mapping as seen by the client-side X.Org server is dumped and periodically applied to the remote side (via xmodmap.) As such, custom keymaps should work out of the box, but there are still problem reports every now and then about messed up (standard) layouts.
I don't know exactly how Windows clients are being handled - especially since X11 is a third-party application there. I would assume it has some autodetection for the current keymap based on the Windows keyboard input settings, but that likely only works for standard keymaps. No idea how well, if even at all, custom keymaps are supported there.
Question 2: Font handling. I don't get the same set of fonts when I run through x2go as I get when using VNC as some directories are missing from the font path. Trying to manually add those from inside the x2go session ("xset +fp /some/path/that/works/in/vnc/") gives an error. Is there something special with the font handling in x2go that is not compatible with all X11 fonts? Running the same xset command from inside VNC succeeds without problem on the same machine.
That's possible, although all fonts and especially the standard fonts directories should be supported. The important thing to know is that X2Go wraps around nx-libs, which is a fork of X.Org 6.9 with some patches applied by NoMachine and us. Hence, newer features that are exclusively supported by newer X.Org server versions are most likely not available. Also, the tools (c.f., "xset") as shipped by newer X.Org implementations may be incompatible with the old "private" X server (though breaking changes on that front are rare.)
Mihai