Package: x2goserver
Version: 4.0.1.19-010640ubuntu16.04.1
With the most recent updates to Ubuntu 16.04 (moving kernel to 4.4.0-18-generic Apr 6) x2goserver suddenly fails to start. The relevant error message in .xsession-x2go-errors is:
13 XSession-x2go: X session started for ddd at Fri Apr 8 17:52:25 EDT 2016
14 localuser:ddd being added to access control list
15 /etc/x2go/Xsession: 3: [: x: unexpected operator
16 mate-session[3684]: GLib-GIO-CRITICAL: g_settings_schema_source_lookup: assertion 'source != NULL' failed
17 mate-session[3684]: GLib-GIO-ERROR: No GSettings schemas are installed on the system
18 aborting...
I have Ubuntu 16.04 installed on a physical machine and also as a KVM virtual machine. In each case after the most recent updates x2goserver fails to start with the same message as above.
Processing commands for control(a)bugs.x2go.org:
> archive 586
Bug #586 {Done: Juri Grabowski <x2go-dev(a)jugra.de>} [x2goserver] X2Go session sometimes slows to a crawl
archived 586 to archive/86 (from 586)
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
586: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=586
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
Processing commands for control(a)bugs.x2go.org:
> close 586
Bug #586 [x2goserver] X2Go session sometimes slows to a crawl
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
586: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=586
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
Processing control commands:
> close -1
Bug #1507 [pyhoca-cli] pyhoca-cli exits with success (status code 0) if the remote user does not exist
Marked Bug as done
--
1507: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1507
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
Processing control commands:
> close -1
Bug #1586 [pyhoca-cli] pyhoca-cli does not honor the -k (--ssh-privkey) option
Marked Bug as done
--
1586: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1586
X2Go Bug Tracking System
Contact owner(a)bugs.x2go.org with problems
Package: pyhoca-cli
Version: 0.5.0.2
Severity: minor
Client OS: Fedora 22 64-bit (with latest updates. In beta, but about
to be released.)
pyhoca-cli 0.5.0.2-1.fc22 (Fedora's package)
python-x2go 0.5.0.3-1.fc22 (Fedora's package)
Server OS: Fedora 21 64-bit (with latest updates) running in a Docker container
DockerFile: https://github.com/mikedep333/Fedora-Dockerfiles/blob/add-x2go/x2go/x2go-mi…
x2goserver 4.0.1.19-1.fc21 (Fedora's package)
x2goserver-xsession 4.0.1.19-1.fc21 (Fedora's package)
nxagent 3.5.0.29-1.fc21 (Fedora's package)
x2goagent 3.5.0.29-1.fc21 (Fedora's package)
Note: Even if you are unfamiliar with Docker, you should be able to
make sense of the Dockerfile. Note that it is based on the "fedora"
image, which is a very minimal install of Fedora. Also note that
"start.sh" simply adds a user account named "user" with a fixed
password.
When I connect to a new TERMINAL session (which defaults to
lxterminal), the session appears to work fine. However, at the end, I
often receive an exception like:
x2go.x2go_exceptions.X2GoSessionRegistryException: No session found
for UUID a2f17c6e-fe14-11e4-8e21-001a4a1bd601
I am using this command to connect:
pyhoca-cli --server 127.0.0.1 -p 50000 -N --user user
--add-to-known-hosts --libdebug --debug
See attachment for output.
This bug is reproducible, but not 100% of the time. It seems to be
related to timing. It is usually reproduced when I leave lxterminal
open for 10 seconds. (I close lxterminal by typing "exit" or clicking
the X in the window decoration.) It is usually NOT reproduced when I
leave lxterminal open for 2 seconds.