On Tue, Aug 2, 2011 at 11:09 AM, John A. Sullivan III <[email protected]> wrote: > I wondered if it was because our servers are still using 3.0.1-5 as this > smells like it could be an NXAgent problem. I connected to an X2Go > server using the latest X2GoAgent (3.5.0.2-0~x2go1 > +squeeze~heuler~201107) and experienced the same problem. I have > backleveled my Windows system to 3.0.1-4 to see if the problem goes away > but do not have enough data yet to report. Thanks - John
I am also using server 3.0.1-5. Here is a summary of whether I have seen this bug with different windows client versions (64-bit Windows 7 OS) on server 3.01-5: windows client version bug occurs? ================== 3.01-13 NO 3.01-18 YES 3.99 YES _______________________________________________ X2go-Dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-dev
