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
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 <christsc@gmx.de> To: x2go-user@lists.x2go.org 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
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 <christsc@gmx.de> To: x2go-user@lists.x2go.org 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
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 <christsc@gmx.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org 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 <christsc@gmx.de> To: x2go-user@lists.x2go.org 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
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 <christsc@gmx.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org 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 <christsc@gmx.de> To: x2go-user@lists.x2go.org 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
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 <christsc@gmx.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org 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 <christsc@gmx.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org 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 <christsc@gmx.de> To: x2go-user@lists.x2go.org 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
On 09.04.2015 09:30 PM, Robert Dinse wrote:
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.
Nope, both messages are normal.
Other than that, if you have access to the server, try starting up
xfce4-session locally and see if it works or blows up.
From what i understood, running xfce4-session via ssh -X/-Y worked fine.
I figure it's just a missing x2goserver-xsession package.
Mihai
On Do 09 Apr 2015 21:30:23 CEST, Robert Dinse wrote:
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
This can be ignored. In X2Go Server's x2gostartagent, this dir gets
created on purpose to block creation of the keyboard file. It's hacky,
I know, but when implementing automatic keyboard setup, I did not see
any other option.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Ha ha, I did ignore it since I never had a problem until someone else
posted their logs to look at. But you're right, it is a hack.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Fri, 10 Apr 2015, Mike Gabriel wrote:
Date: Fri, 10 Apr 2015 15:12:01 +0000 From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de> To: Robert Dinse <nanook@eskimo.com> Cc: Christoph Schmidt-Hieber <christsc@gmx.de>, x2go-user@lists.x2go.org Subject: Re: [X2Go-User] X authorization issues
On Do 09 Apr 2015 21:30:23 CEST, Robert Dinse wrote:
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
This can be ignored. In X2Go Server's x2gostartagent, this dir gets created on purpose to block creation of the keyboard file. It's hacky, I know, but when implementing automatic keyboard setup, I did not see any other option.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Hi Christoph,
On 09.04.2015 02:54 PM, Christoph Schmidt-Hieber wrote:
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.
This looks like it's a problem with XFCE (not) starting up.
Please check ~/.xsession-x2go-errors
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.
It doesn't look like your client is misbehaving.
Mihai