On Tue, 2012-03-06 at 18:21 +0100, Mihai Moldovan wrote: > Hi Mike, > > * On 06.03.2012 09:48 AM, Mike Gabriel wrote: > > You should wait for 3.99.1.1, I guess. There is an X-Server detection fix > > (using unix socket, not TCP to connect to the local X-Server) in it. > > Probably. :) I do have a got git-snapshot with this fix in place (or could > easily fetch the newest changes and rebuild), but this "production-ready" > requirement makes me hesitate. ;) > > > > Mihai, is anything else needed to be patched into x2goclient.git currently > > for > > Mac OS X? > > Depends... here's a list of problems I FOUND (but not fixed): > > - sometimes, I have to resume a session, restart the client, suspend the > session > and resume it again for it to be usable (first time resuming will just close > the > connection to the server), BUT IIRC this happens on Linux, too, so I can't > actually blame the OS X part... (plus, it only happens sometimes. :() > - Client seems to be working fine for me on OS X 10.6/Snow Leopard. But: > - has some weird memleak on OSX 10.5 (not always, again...) > - Stephan reported problems on 10.7 which seem to be SSH-related, I've gotta > take a look at that, no idea if I can figure it out though. Looks like a > libssh > problem, but at least I've got some debug output. > > No concrete code fixes from my side yet though. <snip> I have noticed that problem in Linux. I think it is an SSH timing issue. The connecting, suspending, reconnecting is not actually doing anything, I believe, except functioning as a rudimentary clock. If one just waits five minutes after being abruptly disconnected, all reconnects fine :( - John
_______________________________________________ X2Go-Dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/x2go-dev
