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
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fri, 2011-07-22 at 12:10 +0200, Mike Gabriel wrote:
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...
<snip> One of my concerns is that some of the more important issues may be issues with the NX code rather than the X2Go code. What are our capabilities for fixing those kinds of problems? Thanks - John
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.
regards, alex
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Hi Alex,
2011/7/27 Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>:
Unfortunately, I can not reproduce some bugs reported of users on this mailing list - [...] Issues with failed connection on Win7-64
[...] As example, one of our
customers found out, that x2go client on Win7 can not connect to server if Avast antivirus is installed.
I'm one of the users that have reported problems with x2goclient (newer than 3.01-13) on Win 7 x64 and it turned out that the problem was caused by Symantec Endpoint Protection (SEP). When I uninstalled SEP, x2goclient started working. Seems like antivirus (and perhaps firewall) software is the first thing to uninstall (not just disable, really uninstall) when troubleshooting x2goclient on Windows.
Cheers, Daniel
Am 27.07.2011 15:04, schrieb Daniel Lindgren:
Hi Alex,
2011/7/27 Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>:
Unfortunately, I can not reproduce some bugs reported of users on this mailing list - [...] Issues with failed connection on Win7-64
[...] As example, one of our
customers found out, that x2go client on Win7 can not connect to server if Avast antivirus is installed.
I'm one of the users that have reported problems with x2goclient (newer than 3.01-13) on Win 7 x64 and it turned out that the problem was caused by Symantec Endpoint Protection (SEP). When I uninstalled SEP, x2goclient started working. Seems like antivirus (and perhaps firewall) software is the first thing to uninstall (not just disable, really uninstall) when troubleshooting x2goclient on Windows.
Cheers, Daniel
Hallo Daniel,
Yes, it looks like some antiviral software blocking tcp/ip connections between processes. X2go can work correctly even with absolute pnaroidalic configured windows firewall, because no ports, which should be accessed from network are opened on client. But it steel need tcp/ip connections between processes on system. For example, between nxproxy and X-server. I can not explain why various antiviral software doing this, but I can imagine, that there are although other software except X2Go, that couldn't be running because of such antiviruses.
Question to list: Is there a some antiviral software, which can be used with x2go client?
regards, alex
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
2011/7/27 Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de>:
Yes, it looks like some antiviral software blocking tcp/ip connections between processes. X2go can work correctly even with absolute pnaroidalic configured windows firewall, because no ports, which should be accessed from network are opened on client. But it steel need tcp/ip connections between processes on system. For example, between nxproxy and X-server. I can not explain why various antiviral software doing this, but I can imagine, that there are although other software except X2Go, that couldn't be running because of such antiviruses.
Question to list: Is there a some antiviral software, which can be used with x2go client?
I've just installed Microsoft Security Essentials on W7 x64 and x2goclient 3.99.0.0 connects without a problem.
Cheers, Daniel
On Wed, Jul 27, 2011 at 4:47 AM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
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)
That is why there needs to be some way to turn on detailed logging so that people testing on other configurations can send logs to the developers to help find bugs. In my opinion, detailed logging should be a high priority for the clients, especially the Windows client.
You did not mention the freezing bug that me and the other John saw. It seems like it may be related to AJAX. Any idea about what may be causing that one and how to fix it?
On 2011-07-27 15:52, John Williams wrote:
That is why there needs to be some way to turn on detailed logging so that people testing on other configurations can send logs to the developers to help find bugs. In my opinion, detailed logging should be a high priority for the clients, especially the Windows client. Adding google-breakpad [1] seems to be worthwhile. It does not seem to be too complicated. But again, someone must have the time to do so.
Cheers Morty
[1] https://code.google.com/p/google-breakpad/
-- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universität Erlangen-Nürnberg Martensstr. 1 91058 Erlangen
Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty
On Wed, Jul 27, 2011 at 8:34 AM, Moritz Struebe <Moritz.Struebe@informatik.uni-erlangen.de> wrote:
On 2011-07-27 15:52, John Williams wrote:
That is why there needs to be some way to turn on detailed logging so that people testing on other configurations can send logs to the developers to help find bugs. In my opinion, detailed logging should be a high priority for the clients, especially the Windows client. Adding google-breakpad [1] seems to be worthwhile. It does not seem to be too complicated. But again, someone must have the time to do so.
Cheers Morty
It says it is a "crash reporting system". Does it only function when the program has crashed?
Because there are a lot of bugs that I have seen that do not result in crashes. I think detailed logs might help to debug some of the problems that I am seeing.
On Wed, Jul 27, 2011 at 4:47 AM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
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)
That is why there needs to be some way to turn on detailed logging so that people testing on other configurations can send logs to the developers to help find bugs. In my opinion, detailed logging should be a high priority for the clients, especially the Windows client.
You did not mention the freezing bug that me and the other John saw. It seems like it may be related to AJAX. Any idea about what may be causing that one and how to fix it? <snip> I can confirm this is still a very serious problem. I was still in Windows when someone started chatting with me on Zimbra on my X2Go desktop. It literally took me 16 -2 20 second before I could respond to
On Wed, 2011-07-27 at 06:52 -0700, John Williams wrote: them after every single time they typed something even if the chat window was hidden. Needless to say, it made it excruciating to conduct that conversation. It then dawned on me to connect to Zimbra directly via the Internet bypassing X2Go. I was able to carry on the same conversation with no problem whatsoever - John
On Wed, 2011-07-27 at 13:47 +0200, Oleksandr Shneyder wrote: <snip> Thanks, Alex, for taking the time to investigate. I'll comment in the text - John
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.
<snip>
Unfortunately, I can not reproduce some bugs reported of users on this mailing list - Issues with image packaging, Issues with scrolling in firefox
In my reporting, these two issues are related. The slow Firefox scrolling is from using pack=none.
As I mentioned, the packing problem may not be strictly 3.99 but it is definitely a problem. I have it on Windows XP 32 bit, Windows 7 64 bit, Windows Server 2008 64 bit. I can confirm all three connecting to 3.0.1-5 X2GoServer and Windows XP on both 3.0.1-5 and 3.99.0.0.
The XP system was a complete rebuilt from the recovery CD with all the latest patches applied (for hours and hours :( ). It did appear to work correctly with 3.0.1-5 server until I installed PyHoca. That's when the problems started. However, the Windows 7 and Windows Server 2008 systems never had Pyhoca installed. They have a fresh installation of 3.99.0. Oops, 2008 had 3.0.1-4. I just removed it, deleted all related files from Program Files, cleaned out the registry of every reference to x2go and obviouslynice and installed 3.99.0. Same problem immediately.
Issues with delays after pressing Up/Down arrow keys.
This is not so much an issue with Up/Down arrow keys. I was using it as an example of how dramatically slower X2Go is on Windows. I was using email selection in Evolution on a large Inbox to illustrate the point as Evolution has particularly bad screen handling.
<snip>
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.
Quite understood and, as I think you know, I'll do whatever I can do to help but we do need to solve these issues. The packing one is critical. It may be a particular combination of packages and I'll enumerate those next as best I can. However, we can tell our clients to reinstall the client but we can't very well tell them to reinstall their OS to ensure it is clean. We'll need to find out what combination causes this so we can both correct it and warn against it.
I've already mentioned the client sides and the Windows packaging is pretty self contained. Here's what I see on the server side:
3.0.1-5: ii x2goagent 3.4.0-3-1 Special NX-ized client, was developed by NoMachine to handle X sessions un x2goclient <none> (no description available) ii x2gognomebindings 2.0.1-1 Description: x2gognomebindings (GNOME mimetypes for x2go) ii x2gokdebindings 2.0.1-4 x2gokdebindings (KDE mimetypes and icons for x2go) ii x2goprint 3.0.0-1 x2goprint command ii x2goserver 3.0.1-5 x2goserver (daemon and tools) ii nxcomp 3.4.0-1-1 NX compression library ii nxcompext 3.4.0-1-1 Xcompext Library for nxagent ii nxcompshad 3.4.0-1-1 nx based library needed by the x2go system ii nxproxy 3.4.0-2-1 NX compression proxy
3.99: ii x2goagent 3.4.0.5-0~x2go1+squeeze~main~35~build Special NX-ized client, was developed by NoMachine to handle X sessions un x2goclient <none> (no description available) un x2goprint <none> (no description available) ii x2goserver 3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts ii x2goserver-extensions 3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts (extensions) ii nxcomp 3.4.0-1-1 NX compression library ii nxcompext 3.4.0-1-1 Xcompext Library for nxagent ii nxcompshad 3.4.0-1-1 nx based library needed by the x2go system un nxproxy <none> (no description available)
<snip> Where shall we look next? Thanks - John
Hi John,
On Mi 27 Jul 2011 16:44:23 CEST "John A. Sullivan III" wrote:
3.99: ii x2goagent
3.4.0.5-0~x2go1+squeeze~main~35~build Special NX-ized client, was
developed by NoMachine to handle X sessions un x2goclient <none>
(no description available) un x2goprint <none>
(no description available) ii x2goserver
3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts ii x2goserver-extensions
3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts
(extensions) ii nxcomp 3.4.0-1-1
NX compression library ii nxcompext 3.4.0-1-1
Xcompext Library for nxagent ii nxcompshad 3.4.0-1-1
nx based library needed by the x2go system un nxproxy <none>
(no description available)<snip>
Could you use this as installation source for heavy testing like we
currently do (nightly builds)?
deb http://packages.x2go.org/debian squeeze heuler
After upgrading all your packages your package list should look like this:
ii x2goagent 3.5.0.2-0~x2go1+squeeze~heuler~20110720~49~build1 ii x2goserver 3.0.99.5-0~x2go3+squeeze~heuler~20110726~135~build1 ii x2goserver-extensions 3.0.99.5-0~x2go3+squeeze~heuler~20110726~135~build1 un x2goserver-home un x2goserver-one un x2goprint ii libxcomp3 3.5.0-1-0~x2go2+squeeze~heuler~20110630~32~build1 ii libxcompext3 1:3.5.0-1-0~x2go1+squeeze~heuler~20110719~35~build1 un libxcompshad ii libxcompshad3 3.5.0-2-0~x2go2+squeeze~heuler~20110719~24~build1 un nxcomp un nxcompext un nxcompshad
thanks + good luck! Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Wed, 2011-07-27 at 17:07 +0200, Mike Gabriel wrote:
Hi John,
On Mi 27 Jul 2011 16:44:23 CEST "John A. Sullivan III" wrote:
3.99: ii x2goagent
3.4.0.5-0~x2go1+squeeze~main~35~build Special NX-ized client, was
developed by NoMachine to handle X sessions un x2goclient <none>
(no description available) un x2goprint <none>
(no description available) ii x2goserver
3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts ii x2goserver-extensions
3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts
(extensions) ii nxcomp 3.4.0-1-1
NX compression library ii nxcompext 3.4.0-1-1
Xcompext Library for nxagent ii nxcompshad 3.4.0-1-1
nx based library needed by the x2go system un nxproxy <none>
(no description available)<snip>
Could you use this as installation source for heavy testing like we
currently do (nightly builds)? deb http://packages.x2go.org/debian squeeze heulerAfter upgrading all your packages your package list should look like this:
ii x2goagent 3.5.0.2-0~x2go1+squeeze~heuler~20110720~49~build1 ii x2goserver 3.0.99.5-0~x2go3+squeeze~heuler~20110726~135~build1 ii x2goserver-extensions 3.0.99.5-0~x2go3+squeeze~heuler~20110726~135~build1 un x2goserver-home un x2goserver-one un x2goprint ii libxcomp3 3.5.0-1-0~x2go2+squeeze~heuler~20110630~32~build1 ii libxcompext3 1:3.5.0-1-0~x2go1+squeeze~heuler~20110719~35~build1 un libxcompshad ii libxcompshad3 3.5.0-2-0~x2go2+squeeze~heuler~20110719~24~build1 un nxcomp un nxcompext un nxcompshad
<snip> I can certainly give that a try. Is that what the new release is going to be built from or from the ones I have installed. This way I make sure I'm troubleshooting the versions which make sense. Thanks - John
Hi John,
On Mi 27 Jul 2011 17:38:33 CEST "John A. Sullivan III" wrote:
On Wed, 2011-07-27 at 17:07 +0200, Mike Gabriel wrote:
Hi John,
On Mi 27 Jul 2011 16:44:23 CEST "John A. Sullivan III" wrote:
3.99: ii x2goagent 3.4.0.5-0~x2go1+squeeze~main~35~build Special NX-ized client, was developed by NoMachine to handle X sessions un x2goclient <none> (no description available) un x2goprint <none> (no description available) ii x2goserver 3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts ii x2goserver-extensions 3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts (extensions) ii nxcomp 3.4.0-1-1 NX compression library ii nxcompext 3.4.0-1-1 Xcompext Library for nxagent ii nxcompshad 3.4.0-1-1 nx based library needed by the x2go system un nxproxy <none> (no description available)
<snip>
Could you use this as installation source for heavy testing like we currently do (nightly builds)? deb http://packages.x2go.org/debian squeeze heuler
After upgrading all your packages your package list should look like this:
ii x2goagent 3.5.0.2-0~x2go1+squeeze~heuler~20110720~49~build1 ii x2goserver 3.0.99.5-0~x2go3+squeeze~heuler~20110726~135~build1 ii x2goserver-extensions
3.0.99.5-0~x2go3+squeeze~heuler~20110726~135~build1 un x2goserver-home un x2goserver-one un x2goprint ii libxcomp3 3.5.0-1-0~x2go2+squeeze~heuler~20110630~32~build1 ii libxcompext3 1:3.5.0-1-0~x2go1+squeeze~heuler~20110719~35~build1 un libxcompshad ii libxcompshad3 3.5.0-2-0~x2go2+squeeze~heuler~20110719~24~build1 un nxcomp un nxcompext un nxcompshad<snip> I can certainly give that a try. Is that what the new release is going to be built from or from the ones I have installed. This way I make sure I'm troubleshooting the versions which make sense. Thanks - John
Yes, the packages in the list are very likely to be that what we want
to be seen released as Baikal (+fixes still to come).
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Wed, 2011-07-27 at 10:44 -0400, John A. Sullivan III wrote:
On Wed, 2011-07-27 at 13:47 +0200, Oleksandr Shneyder wrote: <snip> Thanks, Alex, for taking the time to investigate. I'll comment in the text - John
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.
<snip>
Unfortunately, I can not reproduce some bugs reported of users on this mailing list - Issues with image packaging, Issues with scrolling in firefox
In my reporting, these two issues are related. The slow Firefox scrolling is from using pack=none.
As I mentioned, the packing problem may not be strictly 3.99 but it is definitely a problem. I have it on Windows XP 32 bit, Windows 7 64 bit, Windows Server 2008 64 bit. I can confirm all three connecting to 3.0.1-5 X2GoServer and Windows XP on both 3.0.1-5 and 3.99.0.0.
The XP system was a complete rebuilt from the recovery CD with all the latest patches applied (for hours and hours :( ). It did appear to work correctly with 3.0.1-5 server until I installed PyHoca. That's when the problems started. However, the Windows 7 and Windows Server 2008 systems never had Pyhoca installed. They have a fresh installation of 3.99.0. Oops, 2008 had 3.0.1-4. I just removed it, deleted all related files from Program Files, cleaned out the registry of every reference to x2go and obviouslynice and installed 3.99.0. Same problem immediately.
Issues with delays after pressing Up/Down arrow keys.
This is not so much an issue with Up/Down arrow keys. I was using it as an example of how dramatically slower X2Go is on Windows. I was using email selection in Evolution on a large Inbox to illustrate the point as Evolution has particularly bad screen handling.
<snip>
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.
Quite understood and, as I think you know, I'll do whatever I can do to help but we do need to solve these issues. The packing one is critical. It may be a particular combination of packages and I'll enumerate those next as best I can. However, we can tell our clients to reinstall the client but we can't very well tell them to reinstall their OS to ensure it is clean. We'll need to find out what combination causes this so we can both correct it and warn against it.
I've already mentioned the client sides and the Windows packaging is pretty self contained. Here's what I see on the server side:
3.0.1-5: ii x2goagent 3.4.0-3-1 Special NX-ized client, was developed by NoMachine to handle X sessions un x2goclient <none> (no description available) ii x2gognomebindings 2.0.1-1 Description: x2gognomebindings (GNOME mimetypes for x2go) ii x2gokdebindings 2.0.1-4 x2gokdebindings (KDE mimetypes and icons for x2go) ii x2goprint 3.0.0-1 x2goprint command ii x2goserver 3.0.1-5 x2goserver (daemon and tools) ii nxcomp 3.4.0-1-1 NX compression library ii nxcompext 3.4.0-1-1 Xcompext Library for nxagent ii nxcompshad 3.4.0-1-1 nx based library needed by the x2go system ii nxproxy 3.4.0-2-1 NX compression proxy
3.99: ii x2goagent 3.4.0.5-0~x2go1+squeeze~main~35~build Special NX-ized client, was developed by NoMachine to handle X sessions un x2goclient <none> (no description available) un x2goprint <none> (no description available) ii x2goserver 3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts ii x2goserver-extensions 3.0.99.5-0~x2go3+squeeze~main~78~buil X2go server daemon scripts (extensions) ii nxcomp 3.4.0-1-1 NX compression library ii nxcompext 3.4.0-1-1 Xcompext Library for nxagent ii nxcompshad 3.4.0-1-1 nx based library needed by the x2go system un nxproxy <none> (no description available)
<snip> Where shall we look next? Thanks - John
<snip> OK - I'm sure now that I am in the Twilight Zone! The packing problem has mysteriously disappeared from the Windows XP system. We've made no changes to the systems. I have not checked the Windows 2008 or Windows 7 systems since a few hours ago when I reported they had the packing problem.
I'd really like to find out what it is because it is crippling when it occurs and I have no idea how it fixed :( - John
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:
Full screen toggles do not work in Windows - no magic pixel, AltCtl-M, AltCtl-F.
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!
I get a knotify: no process found error when exiting the Windows session.
Evolution selection (as a representative graphics issue) is still painfully slow
Thanks - John
Am 27.07.2011 18:44, schrieb John A. Sullivan III:
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:
Full screen toggles do not work in Windows - no magic pixel, AltCtl-M, AltCtl-F.
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!
1 and 2 are xvcsrv issues. As I can remember, It was your idea to start X in full screen mode by full screen X2Go session. The magic pixel and AltCtl-M, AltCtl-F are possible to use only with window manager (on windows only if vcxsrv started in rootless mode). The only way to do this with vcxsrv in full screen mode is find a WID of vcxsrv and send WS_MINIMIZE to it main window. To make it possible we should modify both
- x2goagent and x2goclient. My opinion - it is wrong idea. Vcxsrv should be started in rootless mode even for full screen X2Go sessions. If it is not working correctly, we should communicate with developers of vcxsrv to solve this issue. The same is with alt+tab. This events should catch vcxsrv. You can specify by x2goclient the X-server you want to use and the command line arguments to starting it. As far as you find a best combination of vcxsrv version and command line arguments I'll make it default.
- I get a knotify: no process found error when exiting the Windows session.
old workaround for kde3, I'll take care about it.
- Evolution selection (as a representative graphics issue) is still painfully slow
Still can not reproduce it. But even if I can, it is a nxlib problem and will be not easy to solve. All output of nxlibs you can find on client and server side in ~/.x2go folder. Have you this problem only with recent versions of nx or was it always present? If it is a new problem, please find a last version of nxlibs without this problem, it can help to find a bug by researching of changelogs and diffs.
regards
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
Still can not reproduce it. But even if I can, it is a nxlib problem and will be not easy to solve. All output of nxlibs you can find on client and server side in ~/.x2go folder. Have you this problem only with recent versions of nx or was it always present? If it is a new problem, please find a last version of nxlibs without this problem, it can help to find a bug by researching of changelogs and diffs.
If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
Am 28.07.2011 08:51, schrieb John Williams:
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
I don't think, that is a client problem. X2Go client 3.01-13 using the same version of nxproxy as the 3.01-19. As I understood this is not a specific windows problem? this problem exists although with linux client?
-- Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
On Wed, Jul 27, 2011 at 11:59 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
I don't think, that is a client problem. X2Go client 3.01-13 using the same version of nxproxy as the 3.01-19. As I understood this is not a specific windows problem? this problem exists although with linux client?
What do you mean? I can suspend the session in Windows client 3.99 (which does have the freezing issue), then resume the same session in Windows client 3.01-13, and the freezing issue is completely gone. Sounds like a client issue to me.
Am 28.07.2011 09:50, schrieb John Williams:
On Wed, Jul 27, 2011 at 11:59 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
I don't think, that is a client problem. X2Go client 3.01-13 using the same version of nxproxy as the 3.01-19. As I understood this is not a specific windows problem? this problem exists although with linux client?
What do you mean? I can suspend the session in Windows client 3.99 (which does have the freezing issue), then resume the same session in Windows client 3.01-13, and the freezing issue is completely gone. Sounds like a client issue to me.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Ok, I see. I'll try reproduce it.
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
On Thu, 2011-07-28 at 08:59 +0200, Oleksandr Shneyder wrote:
Am 28.07.2011 08:51, schrieb John Williams:
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
I don't think, that is a client problem. X2Go client 3.01-13 using the same version of nxproxy as the 3.01-19. As I understood this is not a specific windows problem? this problem exists although with linux client?
<snip> Windows only for me. Thanks - John
On Thu, 2011-07-28 at 07:38 -0400, John A. Sullivan III wrote:
On Thu, 2011-07-28 at 08:59 +0200, Oleksandr Shneyder wrote:
Am 28.07.2011 08:51, schrieb John Williams:
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
I don't think, that is a client problem. X2Go client 3.01-13 using the same version of nxproxy as the 3.01-19. As I understood this is not a specific windows problem? this problem exists although with linux client?
<snip> Windows only for me. Thanks - John
<snip> In fact, this one needs some serious attention. I'm back in a Windows world today and I'm amazed at how patient our clients have been. This is unusable. One can't be expected to wait 20 seconds between mouse clicks or keyboard strokes but that is what is happening when this bug kicks in. What should take twenty seconds literally takes five minutes!
Again, this is only in Windows and only when using X2Go - John
On Mon, Aug 1, 2011 at 4:16 PM, John A. Sullivan III <jsullivan@opensourcedevel.com> wrote:
On Thu, 2011-07-28 at 07:38 -0400, John A. Sullivan III wrote:
On Thu, 2011-07-28 at 08:59 +0200, Oleksandr Shneyder wrote:
Am 28.07.2011 08:51, schrieb John Williams:
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
X2go-Dev mailing list X2go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
I don't think, that is a client problem. X2Go client 3.01-13 using the same version of nxproxy as the 3.01-19. As I understood this is not a specific windows problem? this problem exists although with linux client?
<snip> Windows only for me. Thanks - John
<snip> In fact, this one needs some serious attention. I'm back in a Windows world today and I'm amazed at how patient our clients have been. This is unusable. One can't be expected to wait 20 seconds between mouse clicks or keyboard strokes but that is what is happening when this bug kicks in. What should take twenty seconds literally takes five minutes!
Again, this is only in Windows and only when using X2Go - John
I concur. This is the most important bug as far as I am concerned. It is stopping me from running any windows client after 3.01-13 (except for testing purposes). I've been running 3.01-13 for months now in 64-bit Windows 7 with only a few bugs that are merely annoying, but I have never been able to run anything after 3.01-13 due to this bug which is a show stopper.
On 2011-08-02 01:34, John Williams wrote:
I concur. This is the most important bug as far as I am concerned. It is stopping me from running any windows client after 3.01-13 (except for testing purposes). I've been running 3.01-13 for months now in 64-bit Windows 7 with only a few bugs that are merely annoying, but I have never been able to run anything after 3.01-13 due to this bug which is a show stopper.
Have you looked into the issues using rdp? There are several network tweaks that are supposed to help - they might help here, too.
Cheers Morty
-- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universität Erlangen-Nürnberg Martensstr. 1 91058 Erlangen
Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty
On Tue, 2011-08-02 at 09:50 +0200, Moritz Struebe wrote:
On 2011-08-02 01:34, John Williams wrote:
I concur. This is the most important bug as far as I am concerned. It is stopping me from running any windows client after 3.01-13 (except for testing purposes). I've been running 3.01-13 for months now in 64-bit Windows 7 with only a few bugs that are merely annoying, but I have never been able to run anything after 3.01-13 due to this bug which is a show stopper.
Have you looked into the issues using rdp? There are several network tweaks that are supposed to help - they might help here, too.
<snip> Yes, I appreciated the lead and spent a few hours playing with tweaking the autotuning parameters even though the description didn't seem to quite apply - those problems seemed more generic. Alas, it did not fix the problem - John
On 2011-07-28 08:51, John Williams wrote:
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
Still can not reproduce it. But even if I can, it is a nxlib problem and will be not easy to solve. All output of nxlibs you can find on client and server side in ~/.x2go folder. Have you this problem only with recent versions of nx or was it always present? If it is a new problem, please find a last version of nxlibs without this problem, it can help to find a bug by researching of changelogs and diffs. If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
Maybe it actually is a windows-issue, that was introduced by changing the ssh-backend - or rather did not trigger with the old one: https://encrypted.google.com/search?q=win7+slow+rdesktop
Cheers Morty
-- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universität Erlangen-Nürnberg Martensstr. 1 91058 Erlangen
Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty
Am 28.07.2011 09:02, schrieb Moritz Struebe:
On 2011-07-28 08:51, John Williams wrote:
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
Still can not reproduce it. But even if I can, it is a nxlib problem and will be not easy to solve. All output of nxlibs you can find on client and server side in ~/.x2go folder. Have you this problem only with recent versions of nx or was it always present? If it is a new problem, please find a last version of nxlibs without this problem, it can help to find a bug by researching of changelogs and diffs. If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
Maybe it actually is a windows-issue, that was introduced by changing the ssh-backend - or rather did not trigger with the old one: https://encrypted.google.com/search?q=win7+slow+rdesktop
Cheers Morty
Hi Morty, I think, John has said, that he has this issue with linux client although.
-- Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Am 28.07.2011 09:09, schrieb Oleksandr Shneyder:
Am 28.07.2011 09:02, schrieb Moritz Struebe:
On 2011-07-28 08:51, John Williams wrote:
On Wed, Jul 27, 2011 at 11:46 PM, Oleksandr Shneyder <oleksandr.shneyder@obviously-nice.de> wrote:
Still can not reproduce it. But even if I can, it is a nxlib problem and will be not easy to solve. All output of nxlibs you can find on client and server side in ~/.x2go folder. Have you this problem only with recent versions of nx or was it always present? If it is a new problem, please find a last version of nxlibs without this problem, it can help to find a bug by researching of changelogs and diffs. If that is the same issue as the freezes (or extremely slow response) that I see when I open a gmail tab in firefox, then the issue is completely absent with Windows x2goclient 3.01-13.
Maybe it actually is a windows-issue, that was introduced by changing the ssh-backend - or rather did not trigger with the old one: https://encrypted.google.com/search?q=win7+slow+rdesktop
Cheers Morty
Hi Morty, I think, John has said, that he has this issue with linux client although.
we have tested evolution and gmail in firefox with recent versions of client and server on linux - no issues. I'll try it tomorrow with windows client.
regards,
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Hi, Alex. Thanks again for taking this seriously. I'll respond in the text - John
On Thu, 2011-07-28 at 08:46 +0200, Oleksandr Shneyder wrote:
Am 27.07.2011 18:44, schrieb John A. Sullivan III:
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:
Full screen toggles do not work in Windows - no magic pixel, AltCtl-M, AltCtl-F.
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!
1 and 2 are xvcsrv issues. As I can remember, It was your idea to start X in full screen mode by full screen X2Go session. The magic pixel and AltCtl-M, AltCtl-F are possible to use only with window manager (on windows only if vcxsrv started in rootless mode). The only way to do this with vcxsrv in full screen mode is find a WID of vcxsrv and send WS_MINIMIZE to it main window. To make it possible we should modify both
- x2goagent and x2goclient. My opinion - it is wrong idea. Vcxsrv should be started in rootless mode even for full screen X2Go sessions. If it is not working correctly, we should communicate with developers of vcxsrv to solve this issue.
That makes sense except, if I remember correctly, there is a difference between full screen and rootless. If I choose fullscreen, it truly is full screen and the user perceives only one desktop. It is as if their X2Go desktop is their only desktop and they do not have the problem of frequently closing their desktop accidentally when closing a maximized application, i.e., clicking on the wrong "x" in the top corner. This setting is highly desirable for those who work only or primarily in their X2Go desktops (the majority of our clients).
In rootless, the X2Go desktop is still placed within a Windows but it takes the entire available area aside from the window decorations. This is highly desirable for those who frequently toggle between their physical and x2go desktops.
I would think we would want to accommodate both (and more!) styles of work. When in full screen mode, my desire would be that the keystrokes would work as if the x2go desktop was the only desktop, i.e., Alt Tab cycles through the x2go desktop apps.
The same is with alt+tab. This events should catch vcxsrv. You can specify by x2goclient the X-server you want to use and the command line arguments to starting it. As far as you find a best combination of vcxsrv version and command line arguments I'll make it default.
- I get a knotify: no process found error when exiting the Windows session.
old workaround for kde3, I'll take care about it.
- Evolution selection (as a representative graphics issue) is still painfully slow
Still can not reproduce it. But even if I can, it is a nxlib problem and will be not easy to solve. All output of nxlibs you can find on client and server side in ~/.x2go folder. Have you this problem only with recent versions of nx or was it always present? If it is a new problem, please find a last version of nxlibs without this problem, it can help to find a bug by researching of changelogs and diffs.
I'll have a look and try to dig deeper. It is a Windows only problem (or perhaps I should say Windows exacerbated).
As I mentioned earlier, I do have a concern that a number of these issues may not be specifically X2Go but rather vcxsrv or NX. The vcxsrv dev has been fabulously supportive. I don't know about NX or if we have the capability to fix it ourselves. Thanks again - John <snip>
-
Daniel Lindgren -
John A. Sullivan III -
John Williams -
Mike Gabriel -
Moritz Struebe -
Oleksandr Shneyder