Release 3.1.1 · TurboVNC/turbovnc

Assets

turbovnc-3.1.1.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 3.0.2 and Adoptium OpenJDK 17.0.10+7.

A new build of TurboVNC-3.1.1-arm64.dmg was uploaded on 2024-02-21 to fix an error ("JRELoadError"), caused by an oversight in the official TurboVNC build scripts, that occurred when launching the TurboVNC Viewer.

Code Quality: Stable
Current Support Category: Active

By default, each instance of the Linux TurboVNC Server now listens on the abstract Unix domain socket, in addition to the pathname Unix domain socket (under /tmp/.X11-unix), associated with its X display number. This prevents recent versions of GDM, when configured with WaylandEnable=false, from attempting to use Display :1 for the local session if a TurboVNC session is already using Display :1. The previous behavior can be restored by passing -nolisten local to vncserver or adding -nolisten local to the $serverArgs variable in turbovncserver.conf.
The vncserver script now checks whether the abstract Unix domain socket associated with an X display number is in use before assuming that the display number is available.
Fixed an issue in the Windows TurboVNC Viewer whereby an F10 key press, followed by an F10 key release, caused the keyboard focus to be redirected to the system menu, and subsequent keystrokes were consumed by the system menu until F10, left Alt, or Esc was pressed to dismiss the menu.
Fixed an issue whereby GTK applications (including the GNOME window manager) running in a TurboVNC session attempted to display to a local Wayland session if one was active.