• Documentation
  • »
  • Release notes
  1. 5.2.2, released 3rd December 2014

    • Windows

      • The DisplayDevice VNC parameter now remotes virtual monitors that have been force-detected.
      • FIXED: vnckeyhelper.exe, a support utility that enables connected users to perform privileged key presses such as Alt+Tab securely, no longer checks online for revoked certificates.
    • UNIX

      • NEW: Support for Ubuntu 14.10. Note that if you are using VNC Server in Virtual Mode, you will need to change the default desktop environment.
      • FIXED: VNC Server in Virtual Mode no longer crashes on low-color depth displays when a session is shared and a second user connects.
    • Mac OS X

      • NEW: Support for OS X 10.10 (Yosemite).
  2. 5.2.1, released 27th August 2014

    • Windows

      • FIXED: VNC Viewer should now start correctly in all circumstances.
      • FIXED: Active Directory users and groups in different domains can now be registered with VNC Server using the Users & Permissions page of the Options dialog box.
      • FIXED: The Minimize and Maximize buttons on the VNC Viewer shortcut (F8) menu now work correctly.
    • UNIX

      • FIXED: The VNC Server status icon should now appear when you log in to the root user account on a host computer.
    • Mac OS X

      • FIXED: Second and subsequent media keys (such as Volume Up or Mute) are now sent to VNC Server, and the equivalent physical keys on the keyboard attached to the host computer are no longer disabled.
  3. 5.2.0, released 9th June 2014

    • All platforms

      • NEW: VNC is available in French, German, and Spanish. The appropriate language for the desktop of each user is automatically selected. This can be changed (if required) using the Locale VNC parameter.
      • VNC parameters that parse environment variables (such as LogDir) now resolve the syntax $$ to a literal $, for example to accommodate such a character in a folder name.
      • FIXED: The VNC Viewer chat interface no longer prevents a user account password being entered at the Login window or lock screen.
    • Windows

      • Chat and file transfer are no longer separate applications but rather merged into the vncserverui.exe program. To configure chat and file transfer using Group Policy, examine the VNC Server > mode > User Interface policy folder.
      • FIXED: VNC applications can now be run from user accounts with a $ character in the account name.
      • FIXED: Active Directory groups with ‘universal’ scope can now be registered with VNC Server on the Users & Permissions page of the Options dialog, in addition to groups with ‘global’ and ‘domain local’ scope.
    • UNIX

      • VNC Server in Service Mode (vncserver-x11-serviced) and the VNC Server in Virtual Mode daemon (vncserver-virtuald) can now be started using systemctl on Linux distributions that support systemd, such as the latest Fedora.
      • VNC Server now supports PAM session modules, and session actions in pam_umask.so, pam_limits.so, pam_env.so, and pam_unix.so are automatically referenced in /etc/pam.d/vncserver (or equivalent file).
      • Chat is no longer a separate application but rather merged into the vncserverui program. To configure chat using policy, edit the vncserverui-<mode> policy template file.
      • FIXED: VNC hosted on a network share no longer relies on the cacerts.pem file.
    • Mac OS X

      • NEW: VNC Server in Service Mode can lock the computer or start the screensaver when the last VNC Viewer user disconnects (not available under OS X 10.4).
      • The VNC Chat.app no longer reads from the /Library/Preferences/com.realvnc.vncchat.plist file. To configure chat using policy, edit the vncserverui-<mode> policy template file.
      • FIXED: VNC Viewer no longer prevents media keys such as volume or brightness from affecting the client computer.