Mario Becroft | 29 Jul 07:36 2014

Bug#511: Cannot resume session, automatically suspends after connecting

I encountered the same problem, characterised by:

1. Warning about fonts in the log.

2. Session resumes briefly but then automatically suspends after about 1

3. Log messages in ~/x2go/*/session.log as follows:

nxagentReconnectFailedFonts: WARNING! Font server tunneling not retrieved.
nxagentReconnect: WARNING! Unable to retrieve all the fonts currently in use. Mi
ssing fonts have been replaced.
nxagentSighupHandler: WARNING! Ignoring the signal in state [SESSION_GOING_UP].
keyboard file created
Session: Session resumed at 'Tue Jul 29 17:10:00 2014'.
Info: Screen [0] resized to geometry [1920x1200] fullscreen [0].
Session: Suspending session at 'Tue Jul 29 17:10:03 2014'.
Info: Waiting the cleanup timeout to complete.
Session: Session suspended at 'Tue Jul 29 17:10:03 2014'.

The cause of the problem was indeed that some fonts were missing on the
client (a gentoo system). I simply installed all the font packages I
could find one at a time until the problem went away.

In my opinion, the x2go client is not capable of running with missing
fonts, despite the message indicating that missing fonts will be
replaced. I think this may be a bug.

(Continue reading)

Kirill Petrov | 28 Jul 22:08 2014

Bug#475: Mavericks 10.9.4/ X2Go Client V. (Qt - 4.8.5) high CPU usage

Experience the same problem with:
OS X 19.9.4, Mac client  X2Go Client V. (Qt - 4.8.5)

On the remote server I see one CPU completely killed:
21002 filer     20   0 63148  41m 5528 S  66.5  1.7   3:51.08 x2goagent
21323 filer     20   0 20936 4956 2516 S  15.3  0.2   0:53.50 xfce4-settings-
21303 filer     20   0 20336 8688 7120 S   0.7  0.4   0:02.84 xfwm4
21305 filer     20   0 35364  10m 8976 S   0.3  0.5   0:00.72 xfce4-panel

At the same time, as soon as I disconnect. CPU usage of x2goagent goes to 0.

Is it the case that Linux clients don't have this problem?

thank you,

x2go-dev mailing list
x2go-dev <at>
Rok Mandeljc | 28 Jul 22:11 2014

Bug#559: x2goclient: the local user name that is passed to x2gomountdirs command needs to be enclosed in quotation marks

Package: x2goclient

In startX2goMount(), the local user name (cuser) is passed as the third
argument to the x2gomountdirs command that will be executed on the
server side. This user name should be enclosed in quotation marks,
otherwise the x2gomountdirs on server side fails for users who are
unfortunate enough to have put a whitespace character in their Windows
user name.
x2go-dev mailing list
x2go-dev <at>
Michael DePaulo | 26 Jul 17:30 2014

Bug#475: Happens to me too, at least partially

On Mon, Apr 14, 2014 at 6:54 AM, Klaus Ade Johnstad
<klaus <at>> wrote:
> When using x2client on Mac OS X 10.8, I notice that x2goagent
> will consume 90-100% of cpu the whole time, and the load goes much
> higher than when using x2goclient

At work, on our RHEL 6.5 64-bit server running GNOME2 and X2Go Heuler
over the last several months (X2Go is updated monthly) (My default
shell is TCSH for legacy reasons):

Once I observed every process under my x2go session using up tons of
CPU. I had to kill those processes.

I do not think I have observed x2goagent/nxagent using up tons of CPU,
but it has 8 physical cores so it is not noticeable if only 1 is maxed

The client has been X2Go Client 4.0.1.x and on Windows 7 SP1
64-bit. I am running a full GNOME xsession.

> I have seen the "remote UI breakage" that the original reporter
> mentions, the UI becomes really unresponsive after a while, and
> clicking an icon might sometimes only produce a result after 30
> seconds, or nothing at all.

I have observed this problem all the time on the aforementioned server
& client. My workaround is to disconnect & reconnect frequently (or to
use Cygwin X11 manually tunneled over SSH.)

> The server is running Debian Wheeze with x2goserver
> --
> Klaus Ade Johnstad

Jacques-Olivier Goussard | 25 Jul 17:45 2014

Bug#558: Empty $USER env var makes x2go start an infinite loop

Package: x2goserver
Version: x2goserver.x86_64
OS: Centos 5

I accidentally stumbled upon this one: if the $USER env var is empty (in my case that was a bug in my .bashrc that generated that), then X2GO doesn't properly reject and log the connection attempt. The client freezes in 'Connecting' state and the sqllite scripts seem to enter an infinite loop trying to do insert session.
Once I kill the x2gostartagent process, I get the list of calls in and can see that the provided session ID is missing the username part (as USER is empty).
Instead of being stuck in session insertion, the fact that USER is empty should be caught earlier, properly reported in syslog and session cleanly rejected.

x2go-dev mailing list
x2go-dev <at>
Alan Peter Fitch | 25 Jul 00:44 2014

Bug#475: Also seen on Centos 6.5 with Windows 7 client

I've seen this on Centos 6.5 with the Windows 7 x2go client, both

I tried downgrading the client all the way back to 3.11 with no effect.

One interesting point - a colleague running x2goclient on Ubuntu 12 LTS
(client version was 3.99) did *not* experience the problem.

In my environment it makes x2go unusable, so I'm now investigating xpra
to get the resume/suspend functionality.



Alan Fitch
X2Go Bug Tracking System | 24 Jul 06:15 2014

Processed: bug 547

Processing commands for control <at>

> retitle 547 server-side fix for 546: Unable to create SSL tunnel
Bug #547 [x2goclient] main branch fix for 546: Unable to create SSL tunnel:
Changed Bug title to 'server-side fix for 546: Unable to create SSL tunnel' from 'main branch fix for 546:
Unable to create SSL tunnel:'
> reassign 547 x2goserver
Bug #547 [x2goclient] server-side fix for 546: Unable to create SSL tunnel
Bug reassigned from package 'x2goclient' to 'x2goserver'.
No longer marked as found in versions
Ignoring request to alter fixed versions of bug #547 to the same values previously set
End of message, stopping processing here.

Please contact me if you need assistance.

X2Go Bug Tracking System
Contact owner <at> with problems
Christian Thiele | 23 Jul 10:05 2014

Bug#557: x2godbadmin --createdb - error "tekidata_port" does not exist

Package: x2goserver

When I try to convert the database to Postgres comes in the execution of x2godbadmin --createdb  the
following error message:

root <at> ml-rz-sv-x2go1:/var/lib/postgresql# x2godbadmin --createdb
DBD::Pg::st execute failed: ERROR:  column "tekidata_port" does not exist
LINE 5: ...d_port, last_time, uname, fs_port, tekictrl_port, tekidata_p...
                                                             ^ at /usr/sbin/x2godbadmin line 528.
Died at /usr/sbin/x2godbadmin line 528.

I am using Ubuntu 14.04 and Repository nightly 
Michael DePaulo | 23 Jul 04:14 2014

Bug#547: Alex's fix in x2goserver

I can confirm that Alex's commit to x2goserver (rather than
x2goclient) fixes this bug.

Clean user SSHD process if connection between server and client lost.
This should fix error "Global request tcpip-forward failed".;a=commit;h=bf318affee905cf7cdeaa5a248dfd07bc46a8a96

Should I retitle and reassign this bug (#547) to x2goserver? And
should we cherry-pick it for x2goserver release/4.0.0.x &
release/4.0.1.x? We should probably release updated versions of
4.0.0.x (baikal) and 4.0.1.x at least a month before we release
x2goclient Otherwise, people will run into this bug if they
update their clients to but do not update their servers.

erik.devriendt | 22 Jul 18:48 2014

Bug#556: hp-toolbox segfaults when started in x2go MATE session

Package: nx-libs 

Distribution: Linux Mint 17 64-bit. 

hp-toolbox segfaults when started in a x2go MATE session. 

hp-toolbox is a python script, part of the hplip-gui package in Linux Mint 17. 

After unsetting the LD_LIBRARY_PATH environment variable, hp-toolbox starts without segfaulting.
(hp-toolbox started in a shell in a terminal window). 

This could be related to : 

gdb post mortem stack backtrace: 

gdb /usr/bin/python core 
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 
Copyright (C) 2014 Free Software Foundation, Inc. 
License GPLv3+: GNU GPL version 3 or later <> 
This is free software: you are free to change and redistribute it. 
There is NO WARRANTY, to the extent permitted by law. Type "show copying" 
and "show warranty" for details. 
This GDB was configured as "x86_64-linux-gnu". 
Type "show configuration" for configuration details. 
For bug reporting instructions, please see: 
Find the GDB manual and other documentation resources online at: 
For help, type "help". 
Type "apropos word" to search for commands related to "word"... 
Reading symbols from /usr/bin/python...(no debugging symbols found)...done. 

warning: core file may not match specified executable file. 
[New LWP 9421] 
[Thread debugging using libthread_db enabled] 
Using host libthread_db library "/lib/x86_64-linux-gnu/". 
Core was generated by `/usr/bin/python /usr/bin/hp-toolbox'. 
Program terminated with signal SIGSEGV, Segmentation fault. 
#0 0x00007fea545e6720 in _X11TransWritev () 
from /usr/lib/nx/X11/ 
(gdb) bt 
#0 0x00007fea545e6720 in _X11TransWritev () 
from /usr/lib/nx/X11/ 
#1 0x00007fea545c7289 in _XSend () from /usr/lib/nx/X11/ 
#2 0x00007fea545bb379 in XQueryExtension () 
from /usr/lib/nx/X11/ 
#3 0x00007fea545af722 in XInitExtension () from /usr/lib/nx/X11/ 
#4 0x00007fea548a65eb in XextAddDisplay () 
from /usr/lib/nx/X11/ 
#5 0x00007fea54ab9683 in XineramaIsActive () 
from /usr/lib/nx/X11/Xinerama/ 
#6 0x00007fea539fbb8f in ?? () 
from /usr/lib/x86_64-linux-gnu/ 
#7 0x00007fea539fc9ef in ?? () 
from /usr/lib/x86_64-linux-gnu/ 
#8 0x00007fea539e5edc in gdk_display_open () 
from /usr/lib/x86_64-linux-gnu/ 
#9 0x00007fea539b6f4d in gdk_display_open_default_libgtk_only () 
from /usr/lib/x86_64-linux-gnu/ 
#10 0x00007fea53d762d4 in gtk_init_check () 
from /usr/lib/x86_64-linux-gnu/ 
#11 0x00007fea53d762f9 in gtk_init () 
from /usr/lib/x86_64-linux-gnu/ 
#12 0x00007fea5d55d47e in ?? () from /usr/lib/x86_64-linux-gnu/ 
---Type <return> to continue, or q <return> to quit--- 
#13 0x00007fea5d541d61 in QGtkStyle::QGtkStyle() () 
from /usr/lib/x86_64-linux-gnu/ 
#14 0x00007fea5d4cc571 in QStyleFactory::create(QString const&) () 
from /usr/lib/x86_64-linux-gnu/ 
#15 0x00007fea5d1df561 in QApplication::style() () 
from /usr/lib/x86_64-linux-gnu/ 
#16 0x00007fea5d1df955 in QApplicationPrivate::initialize() () 
from /usr/lib/x86_64-linux-gnu/ 
#17 0x00007fea5d1dfa80 in QApplicationPrivate::construct(_XDisplay*, unsigned long, unsigned
long) () from /usr/lib/x86_64-linux-gnu/ 
#18 0x00007fea5d1dfcef in QApplication::QApplication(int&, char**, int) () 
from /usr/lib/x86_64-linux-gnu/ 
#19 0x00007fea5e1e9f3e in ?? () 
from /usr/lib/python2.7/dist-packages/PyQt4/ 
#20 0x00007fea5e1ea131 in ?? () 
from /usr/lib/python2.7/dist-packages/PyQt4/ 
#21 0x00007fea59b2eb4c in ?? () from /usr/lib/python2.7/dist-packages/ 
#22 0x00000000004f5d0b in ?? () 
#23 0x000000000052cc20 in PyEval_EvalFrameEx () 
#24 0x000000000055c594 in PyEval_EvalCodeEx () 
#25 0x00000000005b7392 in PyEval_EvalCode () 
#26 0x0000000000469663 in ?? () 
#27 0x00000000004699e3 in PyRun_FileExFlags () 
---Type <return> to continue, or q <return> to quit--- 
#28 0x0000000000469f1c in PyRun_SimpleFileExFlags () 
#29 0x000000000046ab81 in Py_Main () 
#30 0x00007fea6525eec5 in __libc_start_main () 
from /lib/x86_64-linux-gnu/ 
#31 0x000000000057497e in _start () 
Nito Martinez | 21 Jul 19:04 2014

Question about VERSION file in NXCOMP

Hi al,

I have a question about the VERSION file that you use in the nxcomp directory, it seems to be fixed at 3.5.0.
Is there any reason not to update this? Have you found any issues?

I know there is negotiation about the minor and major versions in between the client, but the patch version doesn´t seem to be affected.

This is basically to be able to track errors and be able to match them up with the commits,

Please let me know if this makes sense,



x2go-dev mailing list
x2go-dev <at>