Guys,
I've got an x2go session where it looks like there's some disagreement
internally between what the state really is on the system. I'm seeing
the following messages in the /var/log/messages file:
Jul 12 22:51:58 x2go-server /usr/sbin/x2gocleansessions[3243]:
john-50-1498570300_stDGNOME_dp24: session status S desynchronized with current
status (R) and session suspend already tried unsuccessfully
Jul 12 22:52:12 x2go-server /usr/bin/x2gosuspend-session: session with ID
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
Jul 12 22:52:30 x2go-server /usr/bin/x2gosuspend-session: session with ID
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
Jul 12 22:52:49 x2go-server /usr/bin/x2gosuspend-session: session with ID
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
Jul 12 22:53:08 x2go-server /usr/bin/x2gosuspend-session: session with ID
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
Jul 12 22:53:28 x2go-server /usr/bin/x2gosuspend-session: session with ID
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
Jul 12 22:53:47 x2go-server /usr/bin/x2gosuspend-session: session with ID
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
Jul 12 22:54:06 x2go-server /usr/bin/x2gosuspend-session: session with ID
john-50-1498570300_stDGNOME_dp24 has been suspended successfully
Note the first line? Where is says the session status is desynchronized? How
would I fix this?
The server is running CentOS 6.9 (Final) x86_64:
# rpm -qa |grep x2go
x2goclient-4.0.1.4-1.el6.x86_64
x2goserver-4.0.1.20-1.el6.x86_64
x2golxdebindings-debuginfo-1.0.2.4-1.1.x86_64
x2goserver-xsession-4.0.1.20-1.el6.x86_64
python-x2go-0.5.0.3-1.el6.noarch
x2goagent-3.5.0.32-3.1.x86_64
x2gognomebindings-2.0.2.1-2.1.x86_64
And my client in a Linux Mint 18.2 x86_64 system with:
> dpkg-query -l |grep x2go
ii nxproxy
2:3.5.0.32-0x2go1+git20170412.734+8.main.1 amd64 NX proxy
ii pyhoca-cli
0.5.0.3-0x2go1+git20170412.224+8.main.1 all Command line X2Go
client written in Python
ii pyhoca-gui
0.5.0.6-0x2go1+git20170413.1337+8.main.1 all Graphical X2Go client
written in (wx)Python
ii python-x2go 0.5.0.4-1
all Python module providing X2Go client API
ii x2go-keyring
2012.07.23~jessie~main~17~build1 all GnuPG keys of all X2Go
developers and the X2Go archive
ii x2goclient
4.1.0.0-0x2go1+git20170413.1549+8.main.1 amd64 X2Go Client application
(Qt4)
Now if I go and sit at the x2go-server system, and use the x2goclient
to connect to the session, it's pretty much going to work, though
sometimes it still fails and I need to wipe my working session. Which
sucks.
I also see, on the client system the following in the file:
$ cat ~/.x2go/S-john-50-1498570300_stDGNOME_dp24/sessions
Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent
session.
Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent
session.
Loop: PANIC! The remote NX proxy closed the connection.
Loop: PANIC! Failure negotiating the session in stage '7'.
Loop: PANIC! Wrong version or invalid session authentication cookie.
But I never use kde as my session, and it's configured to use GNOME
only. I've never used KDE at all, except to run their great CD buring
tool k3db at points.
What other debug info can I provide?
Thanks,
John
_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
