Skip to content

1.0.90 (1.1 beta1)

Pre-release
Pre-release

Choose a tag to compare

@dcommander dcommander released this 30 Jul 00:24

Assets

  • turbovnc-1.0.90.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.
  • The binary packages were built with libjpeg-turbo 1.2.0.

Packaging Changes

  • Solaris/x86 packages are no longer provided.

Support

Code Quality: Beta
Current Support Category: EOL

Documentation

User’s Guide for TurboVNC 1.1 (Beta)

Release Notes

Significant changes relative to 1.0.2:

  1. autocutsel has been replaced with a more robust and configurable clipboard transfer mechanism based on the VNC X11 extension and the vncconfig utility used by RealVNC.

  2. The Unix TurboVNC Server now implements the X RENDER extension, which enables font anti-aliasing and animated cursors and fixes various issues with KDE 4. Additionally, the server now embeds the FreeType library for improved font display and compatibility.

  3. Replaced the broken "software cursor" implementation of rich (full-color) cursor rendering in the X11 TurboVNC Viewer with a proper implementation that uses the Xcursor library. This specifically fixes pointer issues that occurred when connecting to the Unix TigerVNC 1.2 Server.

  4. The Unix TurboVNC Server now implements rich (full-color) cursor encoding, so viewers that support this RFB extension (including TigerVNC 1.2 and later and TurboVNC 1.1 and later) can display full-color animated cursors when connecting to the TurboVNC Server.

  5. Enhanced the screen scaling feature in the Java TurboVNC Viewer and added a GUI option to control it.

  6. Added an idle timeout feature to the Unix TurboVNC Server which, when enabled, will cause it to exit automatically whenever a certain number of seconds have elapsed since the last active VNC viewer connection.

  7. Added a -noxstartup option to vncserver, which prevents it from executing the xstartup.turbovnc script. This is useful for those who may want to occasionally run TurboVNC without a window manager.

  8. Fixed image corruption that occurred when using the Lossless Tight or Lossless Tight + Zlib protocols with the X11 TurboVNC Viewer running on a 16-bit-per-pixel X server.

  9. Fixed TurboVNC Server build on ARM-based Linux systems

  10. Added Xvnc command-line options and authentication configuration file directives for disabling clipboard transfer.

  11. Added two options (-alrqual and -alrsamp) to Xvnc that allow for sending automatic lossless refreshes using JPEG rather than mathematically lossless images.

  12. Fixed an issue whereby the Windows TurboVNC Viewer, when running on Windows 7, would display an all-white image on one of the monitors in a multi-monitor configuration the first time the viewer was switched to full-screen mode.

  13. Changed the default full-screen behavior in the Windows TurboVNC Viewer such that the window only spans multiple monitors if the remote desktop will not fit on a single monitor. Added options to the command line, GUI, and .vnc file to allow users to override this behavior and force full-screen windows to always occupy one monitor or all monitors.

  14. Fixed numerous issues with full-screen mode in the X11 TurboVNC Viewer.

  15. Implemented -autopass option in the Windows TurboVNC Viewer, which works the same as the equivalent option in the X11 TurboVNC Viewer. In both viewers, -autopass can now be used with Unix Login Authentication as well.

  16. Added an option to the F8 menu in the X11 TurboVNC Viewer that allows view-only mode to be enabled/disabled on an active VNC connection.

  17. The TurboVNC Server should now build and run properly on FreeBSD.

  18. Added ZRLE encoding to the Unix TurboVNC Server, which may improve performance with the RealVNC Viewer under certain circumstances.

  19. The Windows TurboVNC Server (WinVNC) is no longer provided, as it was badly broken, and the only way to fix it would have involved a complete re-architecture.

  20. The TurboVNC Server now includes a non-functional implementation of the X Input extension, primarily to avoid crashes in recent versions of GNOME that aren't smart enough to check for that extension's existence before using it.

  21. Implemented an authentication plugin mechanism for the Java TurboVNC Viewer, which allows sites to write their own external class for obtaining Unix login authentication credentials.

  22. Although there were no known issues with the implementation of the automatic lossless refresh feature in TurboVNC 1.0.x, the feature was re-implemented without the use of threads, in order to make it easier to maintain.