Two things I see in the logs:

keyboard file not created: Is a directory

Apr  9 20:10:56 pc5-39 /usr/bin/x2gostartagent: blocking creation of agent's
keyboard file /tmp/.x2go-csh/C-csh-50-1428606653_stDXFCE_dp32/keyboard as
requested by session startup command

     Might try deleting the .x2go-csh contents in /tmp and try again.

     Other than that, if you have access to the server, try starting up
xfce4-session locally and see if it works or blows up.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
 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 Thu, 9 Apr 2015, Christoph Schmidt-Hieber wrote:

Date: Thu, 9 Apr 2015 20:20:06 +0100
From: Christoph Schmidt-Hieber <[email protected]>
To: Robert Dinse <[email protected]>
Cc: [email protected]
Subject: Re: [X2Go-User] X authorization issues

The server-side syslog and session log are attached.

I do not have physical access to this server.

Any ideas?

On Thu, Apr 09, 2015 at 12:05:35PM -0700, Robert Dinse wrote:

     My Debian Wheezy server is pretty generic other than a custom kernel,
and what I've done to the kernel really shouldn't affect x2go's ability
to function except functioning a little faster.

     I would suggest enabling debug logging per the Wiki:

        http://wiki.x2go.org/doku.php/wiki:development:debugging

     Try to make a connection, then look at the logs to see if there is
anything telling there.

     Also, can you bring up an xfce desktop locally on the machine?

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
 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 Thu, 9 Apr 2015, Christoph Schmidt-Hieber wrote:

Date: Thu, 9 Apr 2015 19:45:31 +0100
From: Christoph Schmidt-Hieber <[email protected]>
To: Robert Dinse <[email protected]>
Cc: [email protected]
Subject: Re: [X2Go-User] X authorization issues

Same issue with
4.1.0.0-0x2go1.1~git20150403.1278+wheezy.heuler.1

I don't think it's a client issue because we can connect to an x2go
server (xfce4) running on Ubuntu 14.04.

Any further ideas?

On Thu, Apr 09, 2015 at 08:24:58AM -0700, Robert Dinse wrote:

    I just tried this using the same client version, X2Go Client V. 4.0.3.2
(Qt - 4.8.6), originating from a Ubuntu 14.10 system, and connecting to a
Debian Wheezy server and got a full working xfce desktop.

    The version of server on Wheezy is
4.1.0.0-0x2go1.1~git20150403.1278+wheezy+hueler.1 so perhaps you may want to
try updating your server to this version (the most recent) and see if that
resolves your problem.

    If you need a test account to determine if it is an issue with your
client side setup or server, let me know.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
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 Thu, 9 Apr 2015, Christoph Schmidt-Hieber wrote:

Date: Thu, 9 Apr 2015 13:54:28 +0100
From: Christoph Schmidt-Hieber <[email protected]>
To: [email protected]
Subject: [X2Go-User] X authorization issues

Dear all,

We're having issues connecting to an x2go server running on Debian
Wheezy. Specifically, we cannot connect to an xfce4 desktop from an OS
X client.

The x2go client version is 4.0.3.2 (from MacPorts).
The x2go server version is 4.0.1.19-0x2go2+git20150326.1064+wheezy.main.1
(from the x2go Debian repo)

Connections using plain "ssh -Y" or "ssh -X" work fine.

Connections with x2go to a single application work fine.

The permissions of $HOME/.Xauthority are 600

The owner of  $HOME/.Xauthority is $USER:$USER

The first attempt to connect will simply fail, without valuable error
messages (at least to me), the second attempt will result in:

"Your session was closed before reaching a usable state.
This can be due to the local X server refusing access to the client.
Please check authorization provided by the remote X application."

Debug output from the client is attached.

Any help would be greatly appreciated.

Christoph


--
Christoph Schmidt-Hieber
Wolfson Institute for Biomedical Research
University College London
Gower Street
London WC1E 6BT
UK
Phone +44 (0)7551994016

_______________________________________________
x2go-user mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-user

Reply via email to