Omnissa Horizon Client for Linux Release Notes

Horizon Client for Linux 2603 | 14 APR 2026

This page contains release-related information for Horizon Client for Linux 2603, which enables users to connect to and use remote desktops and published applications using a Linux device.

This page is revised periodically as needed with information about the release. Check back regularly for additions and updates to these release notes.

What's New

Horizon Client for Linux 2603 is released in conjunction with Horizon 8 2603.

MID Parameter in F5 Webtop URI

Added support for the MID parameter in F5 Webtop URI launches to the Horizon Client for Linux, matching Horizon Client for Windows behavior.
Remote Desktop or Application Session Disconnect Keyboard Shortcut

Added support for end users to immediately disconnect from a remote desktop or application session by pressing the Ctrl+Alt+F12 keyboard shortcut. This feature is disabled by default. Administrators can enable it through the viewClient.enableSessionDisconnectHotKey setting.

Resolved Issues

This release includes fixes for the following:

AST-15953: URL redirection issue with published app that launches Epic EMR
AST-11503: Users unable to launch Horizon VDIs after upgrading Horizon client to version 2512
AST-6880: Client is slow on connect when using DP to HDMI adapters

Known Issues

The following sections describe known issues related to the operation and performance of Horizon Client for Linux.

For known issues specific to the use of Horizon Client in a Horizon Cloud Service - Next-Gen environment, see the Horizon Cloud Service - Next-Gen Release Notes.

Browser Redirection

When using Browser Redirection from a remote desktop, drop-down menus on web pages may fail to expand.

Workaround: None
Right-click context menus in Chrome or Edge render incorrectly when BCR is enabled on Linux clients

When using Horizon Client on Linux endpoints (Ubuntu or RHEL), right-click context menus inside Chrome or Edge within a Horizon VDI session may not display correctly when Browser Content Redirection (BCR) is enabled.

Workaround: None

Display

On some HP thin clients that have the HP ThinPro 5.2.0 (T6X52011) operating system, Horizon Client for Linux might display a black screen or crash when user is playing some video on a remote desktop and pressing the fast-rewind button on Windows Media Player.

Workaround: Upgrade the OS to HP ThinPro 6.1.0 (T7X61007) or the latest version.
The Horizon Client for Linux authentication domain list, desktop/application protocol list, and display list appear black on some Linux operating systems.
Because Horizon Client for Linux uses the Linux operating system's GNOME theme, these lists appear black, making them difficult to read.

Workaround: Change the GNOME theme used by the Linux operating system. For example, on an Ubuntu system, install gnome-tweak-tool if it is not yet installed, run gnome-tweak-tool , and change the GTK+ theme from Ambiance to Radiance.
When client users connect to a published application using a multiple-monitor configuration, they may encounter unexpected behavior in the display if they disconnect or reconnect monitors in their configuration.

Workaround: Disconnect from the published application and reconnect again.
Horizon Client does not support the Dark Appearance setting in Linux distributions.

Workaround: None
Power-save settings fail to take effect with mouse focus in desktop window.
If the user's mouse pointer is positioned in a remote desktop window, power-save and screen-saver settings fail to take effect on the client system when the configured timeout is reached.

Workaround: Move the focus away from the desktop window by positioning the mouse pointer outside the desktop window.

HTML5 Multimedia Redirection (HTML5 MMR)

When you open a local URL in Microsoft Edge on the remote desktop, multimedia content is not redirected to the client system as expected.
By default, HTML5 MMR in an Edge browser only works for content situated on a non-local URL. To redirect content from a local URL, you must configure a certain setting for Microsoft Edge.

Workaround: On the remote desktop, open a Command Prompt window and run the following command: CheckNetIsolation LoopbackExempt -a -n=Microsoft.MicrosoftEdge_8wekyb3d8bbwe
HTML5 MMR and Browser Redirection do not work on Ubuntu 24.04 clients.
In Ubuntu 24.04, the setting for restricting unprivileged user namespaces is activated by default. Due to a known Chromium limitation, this setting interferes with the operations of Electron, which is required by the HTML5 MMR and Browser Redirection features.

Workaround: Run the command to deactivate the setting for restricting unprivileged user namespaces: sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

Also, include this command in .bashrc or a similar startup file, to ensure the setting remains deactivated when the client system reboots.

Keyboard and Mouse

Mouse does not work inside the Horizon Blast session when the keyboard layout is switched to Secondary Keyboard Layout

Workaround: Manually add the following configuration option in the /etc/omnissa/config file: RemoteDisplay.allowVMPointerEvent2 = FALSE
Keyboard and mouse do not work when connecting to a remote application from a Raspberry Pi running ThinLinX or Stratodesk.
There is a system conflict when using H.264 decoding with ThinLinX or Stratodesk Raspberry Pi for remote application sessions.

Workaround : Turn off H.264 decoding in the Horizon Blast settings.
Windows shortcuts don't work with seamless window applications.
If there are identical shortcuts with differing functions on the client Linux operating system and a remote Windows operating system, the shortcut for the Windows operating system will not work when a seamless window application is active. Only the shortcut for the Linux operating system takes effect. For example, by default, pressing Alt opens a Search dialog window on an Ubuntu operating system and it shows the application's menu on a Windows operating system. When a seamless window application is active, pressing Alt displays the Ubuntu operating system's Search menu, but does not show the application's menu.

Workaround : Change the shortcut in the host Linux operating system or in the remote Windows operating system so that the shortcuts in the two operating systems do not conflict.

Multimedia Redirection (MMR)

Videos do not play smoothly in remote desktops and sound disappears when MMR is enabled and the network delay is more than 75 ms.

Workaround : Disable MMR when the network delay is more than 75 ms.

Printing

If multiple Horizon clients connect to the same published desktop or published 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.

Real-Time Audio-Video (RTAV)

When a Raspberry Pi 4 client user tries to play RTAV video at custom high resolutions (such as 1280 x 800) not supported by the connected USB webcam, the video fails to display in the remote desktop.

Workaround: Use a standard resolution that is supported by the connected USB webcam.
When a Raspberry Pi 4 client user plays RTAV video at high resolution, the frame rate (FPS) of the video is low due to the limited CPU and memory of the client device.

Workaround: None

Remote Sessions

H.264 does not work for some versions of Stratodesk NoTouch.
The H.264 video codec does not work on client systems running some versions of the Stratodesk NoTouch operating system. By default, some Stratodesk releases use KMS for the graphics mode, instead of FKMS.

Workaround: Configure the system to use FKMS. Go to Configuration > Services > Raspberry Pi and set Graphics Mode to Fkms. Reboot the system to save your changes.
FIDO2 limitation on Raspberry Pi with Stratodesk NoTouch.
FIDO2 authentication does not work when using H.264 codec in full-screen mode on a RaspBerry Pi running Stratodesk NoTouch.

Workaround: Exit full-screen mode to use FIDO2 authentication.
System Tray redirection functionality is not supported.
System Tray redirection functionality is not supported, so you cannot exit a remote application session using the system tray.

Workaround: Use the remote application's UI to end the application session. For example, to exit a Skype session, select the Settings icon and then select File > Exit.
You cannot start an application from the Application Launcher because the launcher is unsupported.

Workaround: Start the remote application via the Linux client's UI.
System hangs may occur when using remote applications from a client system running Stratodesk.

Workaround: Reduce the GPU memory to 128 MB. For example, in Stratodesk running on a Raspberry Pi, go to Configuration > Services > Raspberry Pi and change GPU memory (MB) to 128.

Miscellaneous

.Net-based smart card authentication does not support TLS 1.3.

Workaround: None.
Issues when client system runs pcsc-lite version 1.5.
Smart card removal policy may not work, logging off, shutting down or resetting a Windows remote desktop may result in a black screen, or the Horizon Client menu may become blank for about 10 seconds when a user has smart card sessions to multiple desktops and the user disconnects from one desktop.

Workaround: Upgrade to pcsc-lite 1.7.4 or later.
When a remote desktop is reconnected, Powermic Speechmic does not work with DMO 2022.2.
When a remote desktop is reconnected after being disconnected, Powermic device does not work with dictation on DMO 2022.2. This happens when using a USB split and RTAV solution.

Workaround: Use DMO 2021.4 instead.
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 by adding sound.backendType = alsa to either the ~/.omnissa/config or the /etc/omnissa/config configuration file.
Horizon Client crashes upon connecting to a remote desktop.
This known issue occurs under the following conditions:
- Horizon Client is running on an Ubuntu 20.04 system with Intel Ice Lake or later hardware, and
- Session protocol is Horizon Blast with HEVC 4:4:4 encoding
The Intel media driver that ships by default with Ubuntu 20.04 contains a bug that causes Horizon Client to crash. Later versions of the driver contain a fix for this bug.

Workaround: Update the Intel media driver by installing the latest version of intel-media-va-driver-non-free.

Before You Begin

Note: The supported systems listed below and in the Horizon Client for Linux Guide pertain to the Horizon Client for Linux that Omnissa makes available. In addition, several Omnissa partners offer thin and zero client devices for Horizon deployments. The features that are available for each thin or zero client device, and the operating systems supported, are determined by the vendor and model, and the configuration that an enterprise chooses to use. For information about the vendors and models for these client devices, see the Omnissa Compatibility Guides.

Horizon Client for Linux has been tested and is supported on the following 64-bit operating systems if you use the installer provided by Omnissa:
- Debian 12.11, 13.0
- Ubuntu x64 22.04.5, 24.04.5
- Red Hat Enterprise Linux (RHEL) 8.10, 9.6, 10
Horizon Client for Linux is supported on Raspberry Pi 4 Model B devices running Stratodesk NoTouch Operating System, with some limitations. The supported Horizon Client features include Omnissa Horizon Blast Extreme, Integrated Printing, USB redirection, Real-Time Audio-Video (RTAV), and H.264 decoding (for one monitor at resolution equal to or lower than 1920 x 1080).
Horizon Client for Linux is supported with the latest maintenance release of the following deployment types:
- Omnissa Horizon 8 version 2006 and later
- Omnissa Horizon Cloud Service - Next-Gen
- Horizon Cloud in Microsoft Azure
To install Horizon Client for Linux, download the installer from the Horizon Clients download page.
Horizon Client for Linux does not ship with the GTK+ library, but it does use the library installed on the host system. Make sure your system is up to date with a version of the library that includes fixes for publicly reported security vulnerabilities. A list of the publicly reported security vulnerabilities, and the versions affected, for GTK+ can be found at https://www.cvedetails.com/vulnerability-list/vendor_id-666/GTK.html.
For information about the features that are supported in nested mode, see Omnissa Knowledge Base (KB) article 67248, "Horizon Guidelines for Nested Mode."

For more system requirements and detailed installation instructions, see Horizon Client for Linux Guide.

Information for Distribution Partners

The following deployment instructions and information about library dependencies are provided for Omnissa distribution partners. These instructions describe how to deploy Horizon Client for Linux and individual Horizon Client components using tar.gz packages.

For instructions on how to install Horizon Client for Linux using the .deb or .rpm installer file, see Installing Horizon Client for Linux.

Deployment Instructions

Download the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file from the Horizon Client downloads site and extract the contents of the downloaded tar.gz package to your system, where YYMM is the marketing version number, x.x.x is the internal version number, and yyyyyyyy is the build number.
Navigate to the folder for your CPU instruction set architecture. You will find additional tar.gz packages for individual Horizon Client components. For example, in the x64 folder you will find the following tar.gz packages for Horizon Client.

    Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
    Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
    Omnissa-Horizon-serialportClient-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
    Omnissa-Horizon-USB-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
    Omnissa-Horizon-scannerClient-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
    Omnissa-Horizon-integratedPrinting-YYMM-x.x.x.yyyyyyyy.x64.tar.gz
    Omnissa-Horizon-html5mmr-YYMM-x.x.x-yyyyyyyy.x64.tar.gz
    Omnissa-Horizon-fileAssociation-YYMM-x.x.x-yyyyyyyy.x64.tar.gz

Use the following deployment instructions for each of the tar.gz packages.

Horizon Client for Linux

The Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package contains the Horizon Client binaries. Use the following instructions as a guide for configuring the Horizon Client binary files.

The Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package contains the mandatory binaries used by both display protocols, PCoIP and Horizon Blast. Use the following instructions as a guide for configuring the Horizon Client display protocol files.

Extract the Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package.
Navigate to the extracted folder, Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyyy.ARCH. Move the contents of the usr folder to the /usr folder. Depending on your particular Linux environment, you can choose to use a folder different from /usr.
Extract the contents of the Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz package.
Navigate to the extracted folder, Omnissa-Horizon-PCoIP-YYMM-x.x.x-yyyyyyyy.ARCH , and copy the contents of the usr folder to the /usr folder. Depending on your particular Linux environment, you can choose to use a folder different from /usr.

Note: To keep the attributes intact, use the -a option of the cp command when copying the files from lib folder.

USB Redirection

The Omnissa-Horizon-USB-YYMM-xxx-yyyy.ARCH.tar.gz package contains the binaries used by the USB Redirection feature.

Extract the contents of the Omnissa-Horizon-USB-YYMM-xxx-yyyy.ARCH.tar.gz package.
Navigate to where the package was extracted and copy the extracted folders to the recommended system folders.
- Copy the contents of the usr folder to the /usr folder.
- Copy the contents of the etc folder to the /etc folder.
- Create symbolic links for horizon-USBArbitrator using the following command:
```
sudo ln -s /usr/lib/omnissa/horizon/usb/horizon-USBArbitrator /usr/bin/horizon-USBArbitrator
```
Configure the USB Redirection feature, using the following example for an Ubuntu system as a guide.

Ubuntu example for USB Redirection

Set up USB arbitrator daemon in the system's auto-startup script using one of the following methods, where # refers to 2, 3, 4, or 5, depending on your system's run level.
- Create symbolic links using the following command:
  sudo ln -s /etc/init.d/horizon-USBArbitrator /etc/rc#.d/S50horizon-USBArbitrator
- Add /etc/init.d/horizon-USBArbitrator start in your system's /etc/rc.local file. Make sure /etc/rc.local has the executable permission.
Automatically stop the USB arbitrator daemon before a system reboot or halt using the following command, where # refers to 0 or 6, depending on your system's run level.
sudo ln -s /etc/init.d/horizon-USBArbitrator /etc/rc#.d/K08horizon-USBArbitrator
Manually start, stop, or restart the USB arbitrator daemon when necessary using the following command:
sudo /etc/init.d/horizon-USBArbitrator [start|stop|restart]

Serial Port Redirection

To install the Serial Port Redirection feature, see the README file included in the Omnissa-Horizon-serialportClient-YYMM-x.x.x.yyyyyyyy.ARCH.tar.gz file, which is available with the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file that you downloaded earlier from the Horizon Client downloads site.

Scanner Redirection

To install the Scanner Redirection feature, see the README file included in the Omnissa-Horizon-scannerClient-x.x.x.yyyyyyyy.ARCH.tar.gz file, which is available with the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file that you downloaded earlier from the Horizon Client downloads site.

Integrated Printing

To install the Integrated Printing feature, see the README file included in the Omnissa-Horizon-integratedPrinting-x.x.x.yyyyyyyy.ARCH.tar.gz file, which is available for download from the product downloads site.

HTML5 Multimedia Redirection

To install the HTML5 Multimedia Redirection feature, see the README file included in the Omnissa-Horizon-html5mmr-x.x.x-yyyyyyyy.ARCH.tar.gz file, which is available for download from the product downloads site.

File Type Association

To install the File Type Association feature, see the README file included in the Omnissa-Horizon-fileAssociation-YYMM-x.x.x-yyyyyyyy.ARCH.tar.gz file, which is available with the Omnissa-Horizon-Client-Linux-YYMM-x.x.x-yyyyyyyy.tar.gz file that you downloaded earlier from the product downloads site.

Building Dependencies

The following libraries are required for building and running Horizon Client for Linux.

gcc 6.4 or later

The following environment variables are required for building Horizon Client for Linux with the Seamless Window feature.

export VIEW_LIBCRTBORA=1

After you install the Horizon Client components, locate the /bin directory in the Horizon Client package that you extracted earlier. From that bin directory, run the horizon-client-lib-san script, which checks the build dependencies.

Microsoft Teams Optimization and HID Features

To configure the Teams Optimization and HID-compliant features on a thin client, perform the following steps using an administrator account.

On the thin client, modify the /etc/hosts file by adding the following entry: 127.0.0.1 view-localhost
Set the correct access mode on libwebrtc_sharedlib.so as follows: chmod +755 /usr/lib/omnissa/horizon/vdpService/webrtcRedir/libwebrtc_sharedlib.so
To configure the HID-compliant features, create a file named horizon_hid.rules and add the following entries to it:

SUBSYSTEM=="usb", MODE="0666"
KERNEL=="hidraw*", MODE="0666"

Copy the horizon_hid.rules file to /etc/udev/rules.d.
Reload the udev rules as follows: sudo udevadm control --reload-rules && sudo udevadm trigger

Documentation

Horizon Client for Linux documentation is in the Omnissa Information Hub.

Localized Content for Omnissa Docs

For details on Omnissa's localization strategy, see Announcing Omnissa Localization Support.

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.

Support Contact Information

To receive support and to learn more about support policies, see Omnissa Customer Connect.

For information on filing a support request in Customer Connect and via Cloud Services Portal, see Omnissa Knowledge Base article 6000005.

Questa pagina è stata utile?