TurboVNC/turbovnc 1.2rc

1.1.95 (1.2 rc)

on GitHub

Assets

• turbovnc-1.1.95.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.3 beta1.

Support

Code Quality: Release Candidate
Current Support Category: EOL

Documentation

User’s Guide for TurboVNC 1.2 (Release Candidate)

Release Notes

Significant changes relative to 1.2 beta1:

1. The Mac TurboVNC Viewer no longer has a separate menu for the "About" and "Preferences" options. As is the case with most Mac applications, these options are now accessed from the application menu.

2. Opening VNC viewer connection info (.vnc) files in the OS X Finder or dragging and dropping them onto the Mac TurboVNC Viewer icon now works properly. Additionally, if a connection is already open, dragging and dropping a .vnc file onto the Mac TurboVNC Viewer icon will now open a new connection.

3. VNC viewer connection info (.vnc) files can now be opened in Windows by dragging and dropping them onto the Windows TurboVNC Viewer icon.

4. The Java TurboVNC Viewer can now be built and run with Java 5. Consequently, the Mac TurboVNC Viewer now works with the version of Java shipped with OS X 10.4 and 10.5.

5. Previously, when using the Java TurboVNC Viewer on Mac platforms, the menu bar was still visible in full-screen mode, and the dock was still visible if it was not set to auto-hide. The Java/Mac TurboVNC Viewer now takes advantage of the OS X Lion full-screen feature, if available, to provide a "true" full-screen mode on OS X 10.7 and later. On OS X 10.6 and earlier, the behavior is unchanged.

6. Fixed a regression in the new Java TurboVNC Viewer whereby, when used as an applet, specifying a host other than the web server in the Server parameter had no effect.

7. Fixed various key mapping issues in the Java TurboVNC Viewer:

   • The viewer now differentiates between the numeric keypad versions of the navigation keys (Home, End, etc.) and their equivalents on the main keyboard.
   • The viewer now differentiates between the left and right versions of the modifier keys (Alt, Ctrl, etc.)
   • The viewer now properly handles the AltGr key on international keyboards.
   • Left Alt key sequences on Mac clients can now be used to activate pull-down menus on Linux/Windows servers.
   • The Apple keys on Macintosh keyboards can now be used as Windows keys when connecting to Linux and Windows servers.

8. The Windows TurboVNC Viewer now properly differentiates between the numeric keypad versions of the navigation keys (Home, End, etc.) and their equivalents on the main keyboard.

9. Fixed a minor issue in the Windows TurboVNC Viewer whereby it would trigger an Alt keypress on the remote desktop whenever an AltGr key symbol was typed repeatedly.

10. Added LSB headers to the TurboVNC Server init.d script (tvncserver) in order to avoid insserv errors/warnings with recent Debian releases.

11. The TurboVNC Server can now build its font path from a font catalogue, on systems that support them (such as RHEL 6.) vncserver will now check for the existence of a font catalogue at /etc/X11/fontpath.d and use it if it exists. For systems that do not support font catalogues, vncserver will now check for the existence of the Liberation fonts (used by LibreOffice) and the Ghostscript fonts and add them to the fontpath.

12. Fixed an error that occurred when running /etc/init.d/tvncserver stop with an empty /etc/sysconfig/tvncservers file.

13. Fixed an issue whereby the X11 TurboVNC Viewer would fail with an error message of "Password stored in connection info file is invalid" when loading a connection info file in which the encrypted password contained "00".

14. Fixed an issue with the multi-monitor spanning feature in the Mac/Java TurboVNC Viewer whereby the remote desktop would appear on the secondary monitor instead of the primary monitor when the span mode was set to "Primary" (or when the span mode was set to "Auto" and the remote desktop area was less than the primary monitor area.)