On Mon, Aug 1, 2011 at 4:16 PM, John A. Sullivan III <[email protected]> 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 >> > > <[email protected]> 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 >> > > [email protected] >> > > 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. _______________________________________________ X2go-Dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-dev
