Am 03.02.2012 10:36, schrieb newsgroups.mail2@stefanbaur.de:
Am 03.02.2012 10:13, schrieb Oleksandr Shneyder:
Am 01.02.2012 17:19, schrieb Mike Gabriel:
Dear all,
The X2Go Project it proud to announce a couple of new X2Go component releases:
[...]
- x2goclient (3.99.0.6) [...] http://code.x2go.org/releases/binary-win32/x2goclient/x2goclient-3.99.1.0-se...
[.............] This new release seems to fix the issue reported in https://lists.berlios.de/pipermail/x2go-dev/2012-January/003271.html as well. Coincidence or intentional?
Kind Regards, Stefan
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
Hi Stefan,
I can't reproduce error you have described with previous version of x2goclient also. There is no code changes in version 3.99.1.0 that could fix such bug.
regards, Alex
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home