Am 03.02.2012 11:05, schrieb Oleksandr Shneyder:
Am 03.02.2012 10:36, schrieb [email protected]:
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-setup.exe
[.............]
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
[email protected]
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.
Indeed, the bug is still in there, seems I didn't test thoroughly enough.
Steps to reproduce:
1. Use latest Windows X2Go-Client on Windows 7 Home Premium, 32-bit, German
2. Create a new session, title "b0rked", Host: 192.18.3.123, User: foo,
Session Type: KDE
3. Try to connect to this session by selecting it, entering a random
password, and clicking OK
4. Wait until "Connect failed: No error" appears
5. Application greys out and the usual "not responding"-message pops up
(on Windows)
Step 4 doesn't always happen, so it might take you a while to run into this.
Note: I saw it happen a lot with the older client and had assumed it was
a permanent error; with the newer one, it doesn't happen as often, or I
was just lucky today. ;-) Had I known that before, I would obviously
have mentioned it in my previous posting.
Kind Regards,
Stefan
_______________________________________________
X2Go-Dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/x2go-dev
