Is there a way I can point x2goclient to the location of nxproxy? I've got a symlink in /usr/bin but it isn't seeing that apparently.
Kermit Short DCS-5
On Mon, 2013-10-21 at 10:19 +0000, Mike Gabriel wrote:
On Fr 18 Okt 2013 21:52:53 CEST, Short, Kermit wrote:
Greetings! Thank you to everyone who's helped me up to this point!! I've got the x2goclient and seemingly all the required libraries (used objdump -x "x2goclient" | grep NEEDED) to find out all the required linked libraries), and on the thin client I can launch the x2goclient program and the familiar GUI interface pops up. I can create a session as I normally would, and when I double click the session and try and authenticate, the client contacts the remote x2goserver daemon and creates a session. However, that's where everything stops working. I usually get a black window that pops up with an X2Go watermark in it. Eventually my remote graphical desktop appears in this window and I'm off and running. That black window pop up is not happening on the thin client. The display stays on the credential entry screen and the status simply says 'Finished' and the client goes back to it's typical waiting state.
If I try to connect again, I can see that a session on the remote server daemon exists. I can suspend or terminate it. If I try to resume or create a new session, the aforemention behaviour is repeated...no black x2go window, just 'Finished' and that's it.
Anyone have any ideas? It seems like I'm missing some program or module that the client relies on.
Thanks!
This sounds like nxproxy is missing on the thin client...
Mike