Skip to content

2.0.91 (2.1 beta2)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@dcommander dcommander released this 16 Mar 00:54
2.1beta2
4ea954a

Assets

  • turbovnc-2.0.91.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.5 beta1. This improves encoding performance in the server by about 5-10% across the board, relative to TurboVNC 2.0.2.

Support

Code Quality: Beta
Current Support Category: EOL

Documentation

User’s Guide for TurboVNC 2.1 (Beta)

Release Notes

Significant changes relative to 2.1 beta1:

  1. Fixed an issue in the Java TurboVNC Viewer whereby, when built against libjpeg-turbo 1.5 or later, it would generate the following error: "Class not found: org/libjpegturbo/turbojpeg/TJException" at run time and subsequently fail to accelerate JPEG decompression. TJException is a new class in libjpeg-turbo 1.5, and due to an oversight, VncViewer.jar was not including it.

Significant changes relative to 2.0.2:

  1. The TurboVNC Server can now emulate a subset of the NV-CONTROL X11 extension, in order to support certain 3D applications that rely on this extension to query and set low-level nVidia GPU attributes. See the User's Guide for more details.

  2. The TurboVNC Server now provides full support for the VeNCrypt RFB extensions, including TLS-encrypted security types. TLS encryption is provided by OpenSSL in the official TurboVNC binaries, but GnuTLS can be used instead when building the TurboVNC Server from source. Note that when using the Java TurboVNC Viewer, you must use 2.0.1 or later when connecting to a TurboVNC 2.1 server. Older versions of the Java TurboVNC Viewer had a bug that caused them to lock up when connecting to a server that supports both the Tight and VeNCrypt security extensions.

    Backward compatibility note: because of the addition of this feature, it was necessary to remove the -noauth, -novncauth, -nootp, and -nopam parameters to vncserver, because these parameters could not be emulated exactly using the new VeNCrypt security type selection mechanism. Please use the new -securitytypes parameter instead (see the Xvnc man page for more details.)

  3. TurboVNC's vncserver script now supports the -autokill option from TigerVNC, which causes the server to be killed automatically whenever the startup script finishes (which will usually happen as the result of logging out of the window manager running in the TurboVNC session.) It was possible to accomplish the same thing in earlier versions of TurboVNC by running /opt/TurboVNC/bin/vncserver -fg </dev/null &, but this is more intuitive.

  4. The TurboVNC Server and the Java TurboVNC Viewer (when the latter is run in standalone mode on Un*x/Linux machines, using the TurboVNC Helper library) now support a remote X Input interface whereby extended pointer devices (such as drawing tablets) on the client are cloned in the TurboVNC session, and the events from these devices (including pressure, tilt, etc.) are passed from viewer to server. This was specifically designed for Wacom tablets but should work with other extended pointer devices as well.

    Additionally, the Windows TurboVNC Viewer provides specific support for Wacom drawing tablets by interfacing between the Wacom drivers for Windows and the aforementioned remote X Input interface.

  5. Keyboard grabbing has been implemented in the Java TurboVNC Viewer for Windows, thus allowing special keystrokes (such as Alt-Tab) to be sent to the server.

  6. Added a new option to Xvnc (-pamsession) that will open a PAM session for every viewer that authenticates using the username/password of the user who owns the TurboVNC session and will leave that PAM session open until the viewer disconnects. This feature was specifically implemented in order to allow Kerberos tickets created by PAM to be reused within the TurboVNC session, but the feature may benefit other use cases as well.

  7. Added a new parameter to the Java TurboVNC Viewer (NoReconnect) that can optionally be used to revert the behavior introduced in 2.0 beta1[17].

  8. The controls in the Options dialog of the Windows (native) TurboVNC Viewer have been re-organized into two tabs ("Encoding" and "Connection"), which makes the layout of that dialog more similar to that of the Java viewer's Options dialog.

  9. The keyboard/pointer grabbing feature can now be configured from the Options Dialog in both the Windows and Java TurboVNC Viewers.

  10. Added a -poll option to tvncconfig, which works identically to the -poll option in RealVNC's (and TigerVNC's) vncconfig program. This causes tvncconfig to poll for changes to the clipboard at a specified interval rather than waiting for the X server to inform it of the changes.

  11. The Windows TurboVNC Viewer package now includes a console version of the viewer (cvncviewer.exe), which is useful when debugging or when using the -via and -tunnel options. This version of the viewer is built by default when building TurboVNC on Windows, but it can be disabled by setting the TVNC_WINCONSOLE CMake variable to 0.

Assets 15
Loading