Skip to content

0.3.2

Pre-release
Pre-release
Compare
Choose a tag to compare
@dcommander dcommander released this 29 Jul 23:53
0.3.2
997265f

Assets

  • turbovnc-0.3.2.tar.gz is the official source tarball for this release. The automatically generated "Source code" assets are not supported.
  • Refer to https://TurboVNC.org/Downloads/DigitalSignatures for information regarding the methods used to sign the files in this release and instructions for verifying the signatures.

Release Notes

Significant changes relative to 0.3.1:

  1. Incorporated TightVNC 1.3.8 patches (where applicable)

  2. Now using a single RPM to support multiple Linux distributions.

  3. Fixed a couple of issues in the fallback logic of the default ~/.vnc/xstartup script. It should now properly run fvwm2 or twm if KDE, CDE, or GNOME are not available.

  4. First pass at a Mac build of the TurboVNC Viewer. The Mac version is an X11 Unix app and thus needs to be run inside an xterm. It should otherwise behave and perform identically to the Linux version.

  5. Increased the size of the TurboJPEG compression holding buffer to account for rare cases in which compressing very high-frequency image tiles (specifically parts of the 3D Studio MAX Viewperf test) with high quality levels (specifically Q99 or above) would produce JPEG images that are larger than the uncompressed input.

    Linux users will need to upgrade to the TurboJPEG 1.04 RPM to get this fix. For other platforms, the fix is included in the TurboVNC 0.3.2 packages.

  6. Added -fg switch to vncserver to make it (optionally) run in the foreground. This allows you to kill the VNC server by pressing CTRL-C in the shell you used to start it. When in foreground mode, you can also kill the VNC server by logging out of the window manager inside the VNC session.

  7. The /etc/init.d/tvncserver script, which can be used to launch multiple TurboVNC sessions at boot time, should now work properly on SuSE systems.

  8. Added TurboVNC protocol optimizations to the Java viewer and made its configuration options match the other TurboVNC viewers. The Java viewer still uses a slower codec, so it is about 3X slower in a LAN environment than the native viewer. The Java viewer also lacks double buffering support. But with these new optimizations, the native and Java viewers should now perform similarly over a wide-area network.

  9. Added a -password option to the Windows TurboVNC Viewer to allow one to pass the VNC password as plain text.

Assets 4
Loading