The initial 3.3 beta2 release on Friday had a regression that caused
VirtualGL to be enabled by default in all TurboVNC sessions. Since many
users are already away from the office for the holidays and beta
releases aren't canonical, I decided to yank the release and re-spin it
with a fix, as well as incorporate a last-second fix for
https://github.com/TurboVNC/turbovnc/issues/474. Apologies for the
churn. Normally I would not do things that way, but I was already away
from the office for the holidays as well. This was the most expedient
way to solve the problem without access to my lab equipment. Otherwise,
I would have had to delay the release cycle by another week.
If anyone downloaded the initial 3.3 beta2 release before it was pulled,
you can work around the aforementioned regression by setting
$vglrun = "";
in turbovncserver.conf. (Not a big deal, but it affected the ability of
most users to test the software.) The old packages with the bug had a
build number of 20251219. The new packages with the fix have a build
number of 20251222.
Binaries, source tarball, and change log are here:
https://github.com/TurboVNC/turbovnc/releases/tag/3.3beta2
--
You received this message because you are subscribed to the Google Groups "TurboVNC
User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/turbovnc-users/1a6af53f-c47e-47d2-b176-8185b457f4fc%40virtualgl.org.
