VMware Horizon Client for Linux Release Notes
Horizon Client for Linux 3.4 | 4 June 2015
Last Updated: 4 June 2015
These release notes cover the following topics:
VMware Horizon Client for Linux makes it easy to access your Windows virtual desktop from a supported Linux system with the best possible user experience on the
Local Area Network (LAN) or across a Wide Area Network (WAN).
- Support for Ubuntu 12.04 or 14.04, Red Hat Enterprise Linux (RHEL) 6.6, SUSE Linux Enterprise Desktop (SLED) 11 SP3, and CentOS 6.6 - The Horizon Client installer available from the VMware
Downloads site provides support for these operating systems.
- Unmatched performance - The adaptive capabilities of the PCoIP display protocol are optimized to deliver the best user experience, even over
low-bandwidth and high-latency connections. Your desktop is fast and responsive regardless of where you are.
- Simple connectivity - Horizon Client for Linux is tightly integrated with VMware Horizon for simple setup and connectivity.
- Secure from any location - At your desk or away from the office, your data is delivered securely to you wherever you are. Enhanced certificate checking is
performed on the client. Horizon Client for Linux also supports optional RADIUS and RSA SecurID authentication.
Top of Page
What's New in This Release
Top of Page
The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, and Korean.
Note: To have the client user interface use Simplified Chinese characters, set the client system to use the zh_CN locale. If you set the client system to use
the zh_SG locale, the user interface is displayed in English characters.
Top of Page
Before You Begin
- The OpenSSL library is updated to version openssl-1.0.1m. For your convenience, the Horizon Client installer provided on the VMware Downloads site
downloads and installs the library.
- Horizon Client for Linux 3.4 is supported on the following 32-bit operating systems if you use the installer provided by VMware:
- Ubuntu 12.04 or 14.04
- Red Hat Enterprise Linux (RHEL) 6.6 (Recommended) and 6.5 (Supported)
- SUSE Linux Enterprise Desktop (SLED) 11 SP3
- CentOS 6.6 (Recommended) and 6.5 (Supported)
- VMware Horizon Client for Linux is supported with the latest maintenance release of Horizon View 5.3.x, VMware Horizon 6.0.x, or VMware Horizon 6 version 6.1.x.
- To install, download the installer from the VMware Horizon Client download
- Ubuntu users can also download and install Horizon Client 3.4 and earlier versions from the Ubuntu Software Center. You must enable Canonical Partners and use Synaptic Package Manager to search for and
configure installation of the vmware-view-client package. Note that there might be a delay between the time when Horizon Client is first released by VMware and its availability on the Ubuntu Software
Center. Also note that the latest version of the client that supports Ubuntu 10.04 is Horizon View Client 1.7.
For more system requirements and detailed installation instructions, see
Using VMware Horizon Client for Linux.
Top of Page
Resolved in Horizon Client 3.4
Previously, several issues were encountered when using Japanese-language keyboards.
Workaround for previous releases: In order to use the hiragana/katakana/muhenkan/henkan key from a Japanese USB keyboard, enable 106/109 key keyboard support on the View desktop. For instructions, see the Microsoft KB at
http://support.microsoft.com/kb/822190. If using this KB does not solve the problem, see
Horizon Client for Linux 3.2 required openssl 1.0.1i instead of 0.9.8, but SUSE Linux Enterprise Desktop (SLED) 11 did not support native openssl-1.0.1i. Because the hash links for the trusted CA certificates
under /etc/ssl/cert were different from 0.9.8 and 1.0.1, verification of the server certificate failed.
Workaround for previous releases: After compiling and installing openssl 1.0.1i on SLED 11, rebuild the hash link with c_rehash of openssl-1.0.1i as follows:
The c_rehash file is located under the bin folder of compiled openssl.
Resolved in Horizon Client 3.2
Previously, after a session timeout, the desktop could become unresponsive and after about 45 seconds, you were returned to the desktop selector screen.
This issue has been resolved.
Resolved in Horizon Client 3.1
Previously, if you enabled the group policy setting called "Disable sending CAD when users press Ctrl+Alt+Del" in the remote desktop, then on the Linux client, selecting "Send Ctrl+Alt+Delete" from the menu bar
had no effect and using the Ctrl+Alt+Insert key combination had no effect. This issue has been resolved.
Previously, on Ubuntu 12.04 systems, in the Login dialog box for Horizon Client, if you clicked About VMware Horizon Client, you would not be able to close the About box until you first closed the
Login box. This issue has been resolved.
Previously, after you installed Horizon Client, you could not change the language used by the operating system on the client machine. The Language Support app in system
settings would not start. This issue has been resolved.
Previously, if you used Horizon Client with a Ubuntu 12.04 operating system, the menu bar would not appear on the desktop selector screen if you launched the client with the
--fullscreen parameter. This issue has been resolved.
Previously, the copy and paste feature did not work on Linux systems with ARM processors. This issue has been resolved.
Top of Page
A known security issue can affect Horizon Clients. The issue involves a privilege escalation leveraging glibc. This issue was devised by the Project Zero team as described in CVE-2014-5119. To mitigate
this issue, partners and customers are advised to update the Linux operating system as follows:
When you run the Horizon Client installer, the scan check will always return success for the client compatibility component. To get an accurate compatibility check, you must manually run the following command:
This command will tell you if all required libraries are found in your client system. The scan results for the other components, including PCoIP, USB, RTAV, smart card, and virtual printing, are not affected by
this issue. The scan check for these components returns accurate results.
In some versions of Linux, including CentOS 6.5 and 6.6, the Numlock LED does not work while in a View desktop.
If multiple Horizon clients connect to the same RDS desktop or remote application simultaneously and map to a location-based printer with the same name, the printer appears in the first client session, but not in
later client sessions.
Workaround: For the client sessions in which the printer does not appear, perform a manual refresh. For a remote desktop, press F5 or refresh the Devices and Printers window. For a remote
application, close and reopen the application print dialog box. The location-based printer appears in the printer list.
Virtual printing might not work if you connect to a remote desktop using RDP, open Horizon Client on the remote desktop, launch a nested application session, and then log off and log back in to the desktop.
When you try to print from the nested application, the expected printer list might not appear. This issue only occurs after you log back in to the desktop.
Workaround: Reset the application on the remote desktop. To avoid having to set applications, use PCoIP for both ends of the session-in-session connection. That is, use PCoIP to connect to
the remote desktop and use PCoIP to connect from within the desktop to the nested application. If you are using location-based printing, you can resolve this issue by closing and reopening the application's print
If you use a FreeRDP connection and specify a monitor configuration that conflicts with the configuration the end user chooses, Horizon Client performance becomes poor and the client might stop responding
altogether. For example, the following command for launching Horizon Client would cause problems if the user selected "Full Screen - This Monitor":
vmware-view --enableNla --rdpclient=xfreerdp --xfreerdpOptions="/sec:nla /cert-ignore /p:password /u:crt\administrator /multimon"
As a best practice, avoid specifying FreeRDP options for the disply, such as /multimon or /workarea. Instead, let Horizon Client control the topology.
If you use FreeRDP to connect to a Windows XP or Vista remote desktop, and the client system uses multiple monitors with a combined screen resolution that is larger than the maximum resolution set for the remote
desktop, you will not be able to see the Start menu or taskbar in the remote desktop. For example, if the client system uses two monitors with a screen resolution of 2560x1600 each, this issue occurs.
If your client system is running pcscd version 1.5 and you log off, shut down, or reset a Windows 8.1 remote desktop, Horizon Client freezes with a black screen.
Workaround: Stop the pcscd service or update the version of pcscd to 1.7 or later.
If you use a PulseAudio sound system, you might hear static when setting the volume using guest system volume slider.
Workaround: Use the Linux client system's volume slider or use ALSA audio.
If you connect to a View desktop with FreeRDP and configure the desktop to connect to a separate disk, if the disk name includes non-ASCII characters, the disk name
cannot be displayed correctly in the View desktop. For example, if you use non-ASCII characters in the disk name and then launch Horizon Client with command line option
'--rdpclient=xfreerdp' and '--xfreerdpOptions="/drive:, /home/user"'
the disk name does not appear correctly in the View desktop.
If you use Horizon Client with a Ubuntu 12.04 operating system, if you press the Windows key in a View desktop, the Windows key press is also captured by the client
If you use Horizon Client with a Ubuntu 12.04 operating system, occasionally you might see an issue when launching a View desktop in full screen mode.
Workarounds: Update to the latest patch release of Ubuntu 12.04, or switch to the client operating system by pressing Alt+Tab, and then switch back
to the View desktop session.
Top of Page