Skip to content

3.1.2

Latest
Compare
Choose a tag to compare
@dcommander dcommander released this 08 Aug 19:05
· 11 commits to main since this release

Assets

Support

Code Quality: Stable
Current Support Category: Active

Documentation

User’s Guide for TurboVNC 3.1.2

Release Notes

Significant changes relative to 3.1.1:

  1. The TurboVNC Server now assigns an ordinal ID to every VNC viewer when the viewer connects, and when possible, log entries related to a specific viewer are prefixed by the viewer's ID. The TurboVNC Server now also logs the total number of simultaneously connected viewers.

  2. The TurboVNC Viewer now sends horizontal scroll wheel events to the VNC server. (These events can be generated with horizontal scroll gestures on a trackpad or, with certain mice, by side-clicking the scroll wheel.)

  3. By default, the TurboVNC Server now limits the amount of time that it will wait for a new pointer event from a connected viewer that is dragging the mouse (and thus has exclusive control over the pointer.) This prevents other viewers connected to the same session from being locked out of pointer control indefinitely if a viewer's network connection drops while it is dragging the mouse. A new Xvnc command-line option (-pointerlocktimeout) can be used to specify the time limit.

  4. The RPM and DEB packages generated by the TurboVNC build/packaging system now include a polkit rules file that prevents various authentication dialogs ("Authentication is required to create a color managed device", "Authentication is required to access the PC/SC daemon", "Authentication is required to refresh the system repositories") from popping up when using the GNOME window manager with the TurboVNC Server on Ubuntu 23.10 and later (if the polkitd-pkla package is not installed) and on RHEL 7 and Fedora 19 and later (if the polkit-pkla-compat package is not installed.)

  5. The default X startup script (xstartup.turbovnc) now throws an error, rather than trying to execute xinitrc or twm, if a window manager is specified and the session desktop file for the window manager cannot be found.

  6. Added a new parameter (ExtSSHCommand) to the TurboVNC Viewer that can be used to specify the external SSH client command. In Via/Tunnel SSH command-line templates, including the default ones, %S is now replaced with the value of this new parameter.

  7. Fixed a regression introduced by 3.0 beta1[24] that caused the TurboVNC Server to leak memory when the RFB flow control extensions were used.

  8. Fixed several issues in the TurboVNC Viewer that prevented IPv6 addresses from being used as VNC hostnames.