Stefan,

Q1: So now I'm confused - are you trying to connect to the same server, from both clients? Or are these two different servers, not only two different clients?

My response: I am trying to connect from one x2go client (Mac 10.10.4) to one x2go server (RHEL7). When I login from the x2go client using a non-root account to the x2goserver the session kicks me back to the login screen. When I login from the x2go client using a root account to the x2goserver I am able to connect without any problems.

Q2: It doesn't look like you allowed incoming connections for x2goclient.app yet? Judging from what Mihai (one of our resident Mac experts here on the list) told me, you have to, or X2GoClient won't work

My response: the x2go server is RHEL7, how do you allow incoming connections for x2goclient.app?

The x2goserver is installed and the x2gocleansessions.service is running. Here are the rpms installed and the preceding firewall commands tried.

[root@ ~]# rpm -qa | grep x2go

x2goserver-4.0.1.19-3.el7.x86_64

x2goserver-xsession-4.0.1.19-3.el7.x86_64

x2goagent-3.5.0.31-1.el7.x86_64

x2goclient-4.0.3.1-1.el7.x86_64

[root@ ~]# firewall-cmd --permanent --add-service=x2go

Error: INVALID_SERVICE: x2go

[root@ ~]# firewall-cmd --permanent --add-service=x2gocleansessions.service

Error: INVALID_SERVICE: x2gocleansessions.service

[root@ ~]# firewall-cmd --permanent --add-service=x2goclient.app

Error: INVALID_SERVICE: x2goclient.app

[root@ ~]# firewall-cmd --permanent --add-service=x2goclient

Error: INVALID_SERVICE: x2goclient

[root@ ~]# systemctl status x2gocleansessions.service

x2gocleansessions.service - X2go session cleanup

Loaded: loaded (/usr/lib/systemd/system/x2gocleansessions.service; enabled)

Active: active (running) since Tue 2015-09-15 09:04:18 PDT; 4 weeks 0 days ago

Main PID: 717 (x2gocleansessio)

CGroup: /system.slice/x2gocleansessions.service

└─717 /usr/bin/perl /usr/sbin/x2gocleansessions

Q3: run the following 4 tests on the terminal, compare banner messages

My response: ran the ssh commands suggested but there are no banner differences. I’m able to connect to the x2goserver without issues. Xterm comes up without issues, no error messages.

Q4: xquartz security tab screen shot

My response: both authenticate connections and allow connections from network clients are checked (see attachment)

Q5: are machines on same network

My response: yes they are

Thank you,

Liz

From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov>
Date: Monday, September 28, 2015 at 3:26 PM
To: "x2go-dev@lists.x2go.org" <x2go-dev@lists.x2go.org>
Subject: Re: x2go client session kicks user back to the session login screen

Stephan,

I reinstalled xquartz 2.7.7 and x2goclient 4.0.5 and verified the settings are set to those recommended.

The behavior is happening when regular users attempt to connect to an x2go server. This leads me to believe it could be a permissions issue?

When I attempt to connect as a regular linux user, I get kicked back to the login scree. However when I connect as ‘root’ there are no problems.

CLIENT LOGIN AS REGULAR USER:

I noticed that if I attempt to login as a regular linux user (real), that user gets kicked back to the login screen, here’s the session output:

"Protocol mismatch or no X authentication data”

SERVER:

The /var/log/secure reports:

Sep 28 15:11:34 **** sshd[27639]: Accepted keyboard-interactive/pam for real from ********** port 52380 ssh2

Sep 28 15:11:34 **** sshd[27639]: pam_unix(sshd:session): session opened for user real by (uid=0)

Sep 28 15:11:38 **** su: pam_unix(su:session): session opened for user real by (uid=0)

Sep 28 15:11:38 **** su: pam_unix(su:session): session closed for user real

When I check the status of x2gocleansessions.service:

Sep 28 15:11:36 ******* /usr/sbin/x2gocleansessions[769]: real-50-1443478272_stDKDE_dp32: state file for this session does not exist: /tmp/.x2go-real/C-real-50-1443478272_stDKDE_dp32/state (this can be ignored during session startups)

CLIENT LOGIN AS ROOT:

As root there are no issues.

SERVER:

/var/log/secure shows:

Sep 28 15:21:04 node4 sshd[6137]: Accepted password for root from ********* port 52504 ssh2

Sep 28 15:21:04 node4 sshd[6137]: pam_unix(sshd:session): session opened for user root by (uid=0)

Sep 28 15:21:15 node4 polkitd[1516]: Registered Authentication Agent for unix-session:46638 (system bus name :1.102126 [/usr/libexec/kde4/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale C)

Sep 28 15:21:17 node4 sshd[7291]: Accepted publickey for rmdc from ********** port 50161 ssh2: RSA 81:72:dd:4f:3d:a2:18:ba:ed:77:2a:1d:2e:72:f6:4b

Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session opened for user rmdc by (uid=0)

Sep 28 15:21:17 node4 sshd[7291]: pam_unix(sshd:session): session closed for user rmdc

Sep 28 15:21:23 node4 sshd[7347]: Accepted publickey for root from ********** port 49422 ssh2: RSA 23:2c:8c:a6:fd:aa:80:ae:7e:fa:60:57:5f:e4:c2:98

Sep 28 15:21:23 node4 sshd[7347]: pam_unix(sshd:session): session opened for user root by (uid=0)

Thank you,

Liz

From: Elizabeth Real Chavez <Elizabeth.Real@jpl.nasa.gov>
Date: Thursday, September 24, 2015 at 9:12 AM
To: "x2go-dev@lists.x2go.org" <x2go-dev@lists.x2go.org>
Subject: x2go client session kicks user back to the session login screen

Hello,

I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical.

I’ve attached screen shots of the client session details. The last messages in the session are:

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

x2go client: v4.0.4.0

xquarts: v2.7.7

Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server.

Please advise.

Thank you,

Liz