[X2go-Dev] core dev-team testing x2goclient during next week

[John A. Sullivan III]

On Wed, 2011-07-27 at 13:47 +0200, Oleksandr Shneyder wrote:
> Am 22.07.2011 12:10, schrieb Mike Gabriel:
> > Hi all,
> > 
> > thanks to everyone (esp. to John) for taking such a meticulous look at
> > the latest x2goclient 3.99.0.0 (Win32 version). There obviously seem to
> > be quite some open issues that we have to cross-check on our own
> > development/testing systems.
> > 
> > Alex (the core developer of x2goclient) will do that ASAP, we hope to
> > come up with some feedback, patches, comments by the end of next week.
> > If that gets delayed, I will let you know about the delay and come up
> > with another timeline.
> > 
> > Unfortunately, as X2go is not a commercial project, this cannot be any
> > quicker. We apologize for this!!!
> > 
> > If there are people out there you can read/write C code, please feel
> > free to clone git://code.x2go.org/x2goclient.git and cross-read the code.
> > 
> > Some other problems, however, may arise from x2goagent, as well. So you
> > might use git://code.x2go.org/x2goagent.git for lecture as well...
> > 
> > Greets,
> > Mike
> > 
> 
> Hello all,
> 
> last days I spent some time to test the latest version of x2goclient
> (3.99.0) on different platforms:
> 
> Server
> 
> debian lenny i386, x2goserver-3.0.99-5, nxlibs-3.4.x, x2goagent-3.4.x
> debian squeeze i386, x2goserver-3.0.99-5, nxlibs-3.4.x, x2goagent-3.4.x
> debian squeeze i386, x2goserver-3.99.0.0, nxlibs-3.5.x, x2goagent-3.4.x
> debian squeeze i386, x2goserver-3.99.0.0, nxlibs-3.5.x, x2goagent-3.5.x
> debian squeeze amd64, x2goserver-3.0.99-5, nxlibs-3.4.x, x2goagent-3.4.x
> debian squeeze amd64, x2goserver-3.99.0.0, nxlibs-3.5.x, x2goagent-3.4.x
> debian squeeze amd64, x2goserver-3.99.0.0, nxlibs-3.5.x, x2goagent-3.5.x
> 
> Client
> 
> debian lenny i386
> debian squeeze i386
> debian squeeze amd64
> windows7-32
> windows7-64
> 
> I've tested connections in LAN and over Internet and was able to connect
> and work without any serious issues.
> 
> During tests I've found some bugs:
> 
> - x2goclient crashing some times if user login unsuccessful (f.e. wrong
> password)
> 
> - x2goclient crashing by unexpected output in user console (f.e. there
> is a line in ~/.basrc "cowsay hello" or user shell set to /bin/false )
> 
> - under Windows system tray icon does not disappear on client close.
> 
> I'll fix this bugs ASAP.
> 
> Unfortunately, I can not reproduce some bugs reported of users on this
> mailing list -
> Issues with image packaging,
> Issues with scrolling in firefox
> Issues with delays after pressing Up/Down arrow keys.
> Issues with failed connection on Win7-64
> 
> I can imagine, that some of this bugs are system dependent. X2Go uses
> many components - x2go server, client, nxlibs, nx(x2go)agent. Under
> windows x2goclient starts although X-server, SSH server and Pulseaudio
> server. All this components are depended from many system libraries, for
> example libpng, libjpeg, etc.
> 
> Unfortunately, we can not to test X2Go with all possible combinations of
> software installed on user computer. We running our tests on fresh
> installed OS with default set of software. And default options of
> x2goclient (on Windows with default X-server and default command line
> options)
> 
> If you expecting troubles running X2Go, please try, if it possible, to
> install a "clean" OS, without any additional software (f.e. third-part
> firewalls or antivirals on Windows) If X2Go running on such "clean"
> system, you can compare it with you productive system and find out which
> software blocking functionality of X2Go. As example, one of our
> customers found out, that x2go client on Win7 can not connect to server
> if Avast antivirus is installed.

Hi, Alex.  Although the packing and multi-session problems have
mysteriously vaporized as I reported elsewhere, I can confirm that we
still have the following:

1) Full screen toggles do not work in Windows - no magic pixel,
AltCtl-M, AltCtl-F.

2) AltTab does not work as expected in Full Screen mode - in fact,
rather than scroll through the X2Go desktop applications, it is
currently the only way to break out of full screen!

3) I get a knotify: no process found error when exiting the Windows
session.

4) Evolution selection (as a representative graphics issue) is still
painfully slow

Thanks - John