Skip to content

PCoIP Graphics Agent for Linux 19.05.0 Release Notes

Release Overview

PCoIP Graphics Agent 19.05 for Linux consolidates a number of new features and includes product and security updates.

What's New in This Release

Release 19.05 of the Graphics Agent for Linux includes the following enhancements:

  • Support for PCoIP Ultra, our latest PCoIP protocol enhancements. This is an evolving feature that will continually improve with each release.

  • Clients connecting directly to the PCoIP agent, without using a connection broker, can now be shown a disclaimer message prior to authenticating. The disclaimer must be accepted in order to connect. To use this feature, enable pcoip.enable_disclaimer_auth.

  • The PCoIP Agent for Linux now installs without any USB dependencies. A default installation cannot bridge USB devices.

  • Because installation no longer includes USB dependencies, supporting bridged USB devices now requires an additional installation step.

  • Added support for QEMU/KVM hypervisor.

Important Notes and Requirements

  • When installed on RHEL, the PCoIP Graphics Agent requires access to the  rhel-7-desktop-optional-rpms.  This can be enabled by issue the following yum command:

    • sudo yum-config-manager --enable rhel-7-desktop-optional-rpms

  • PCoIP Graphics Agent for Linux requires a license registration code (for Teradici Cloud Licensing), or a license activation code (for Local License Servers). If you are a new user, request a registration code for a full evaluation.

  • New Cloud Access Software license purchases or renewals can only be activated using PCoIP Agent 2.11 or newer (any agent type).

  • When reporting issues to Teradici, be sure to run pcoip-support-bundler and include the output it generates.

Release Downloads

The Linux Graphics Agent is available through the apt (Ubuntu) or yum (RHEL) command line utility. Refer to Installing Graphics Agent for Ubuntu or Installing Graphics Agent for RHEL for further information.

Related Documents and Software

Release History

VersionDateDescription
19.05May 2019General Availability


For compatibility details, refer to System Requirements in the administrators' guide.

Resolved Issues

Session now successfully starts with Grid 7.1 drivers on a RHEL/CentOS machine | 81155

Previously, session failed to start after picking up Grid 7.1 drivers on a RHEL/CentOS host machine. The issue is now fixed.

Known Issues

Xorg crashes on session start after upgrading to GRID 7.x | 82080

After upgrading to an NVIDIA GRID 7.x driver, incompatible Xorg extensions (like libglx.so) from previous drivers can remain on the machine. These incompatible extensions can cause Xorg to crash, which prevents the PCoIP session from starting.

Workaround

Reinstall the Xorg package so the correct glx Xorg extension is installed.

In RHEL/CentOS:

sudo yum reinstall xorg-x11-server-Xorg

In Ubuntu 16.04/18.04:

sudo apt install --reinstall xserver-xorg-core

Session cannot be started when using stock Ubuntu 18.04 | 81843

When using a standard installation of Ubuntu 18.04, it is possible that a PCoIP session cannot be established and the user will continually receive connection errors.

Workaround

To work around this issue, open /etc/pcoip-agent/pcoip-agent.conf in a text editor and add the following line:

pcoip.desktop_session = ubuntu

See pcoip-agent.conf(8) for more information on this setting.

Mouse cursor does not move with bridged Wacom tablet when using touch | 81505

The mouse cursor does not move as expected when using touch if bridging USB Wacom tablet. It will appear to be stuck to the top left corner of the display. This is due to the tablet's touch feature being seen as a relative pointing device, which is not supported with USB bridging.

Workaround

Force the touch pad mode to use absolute coordinates by creating the following file:

/usr/share/X11/xorg.conf.d/52-pcoip-wacom.conf

Section "InputClass"
        Identifier "PCoIP Wacom USB touchpad force absolute"
        MatchUSBID "056a:*"
        MatchDevicePath "/dev/input/event*"
        MatchIsTouchpad "true"
        Option "Mode" "Absolute"
EndSection

Note that this will not behave in the same way as when connected to a physical PC, as the tablet will be mapped to the entire visible display.

License registration fails when proxy server name resolution takes too long | 78337

The pcoip-register-host command can fail when using a proxy server if resolving the name of the proxy server takes more than 5 seconds.

Workaround

Run pcoip-register-host again, or run pcoip-register-host using the IP address of the proxy server instead of the name.

Graphics Agent for Linux cannot connect after yum upgrade | 78018

Updates to certain X subsystems can override NVidia driver configuration requiring the re-installation of the NVidia driver.

Workaround

Download and install the latest NVidia driver

restart PCoIP to ensure there is no X session running:

sudo systemctl restart pcoip sudo /bin/sh NVIDIA-Linux-x86_64-XXX.XX-grid.run --dkms -s sudo dracut -fv sudo reboot

NVIDIA driver may not load after update | 76941

After updating the NVIDIA Grid driver on a Linux agent system the contents of initramfs may still contain the older NVIDIA Grid driver kernel modules.  On reboot the new NVIDIA driver will not load resulting in an inability to connect via PCoIP.

Workaround

When the system is rebooted, the older kernel modules from the initramfs are loaded again, which means the userspace libraries can't talk to the new driver.

To resolve the issue:

To resolve the issue after the driver is installed but before rebooting:

sudo dracut -fv

To resolve the issue after the driver is installed and after rebooting:

sudo modprobe -r nvidia_drm nvidia_modeset nvidia sudo dracut -fv sudo reboot

Wacom LT may take up to ~25 seconds to register in RHEL/CentOS 7.x | 74752

Due to limitations in the operating system kernel, the tablet may take up to ~25 seconds to show up in RHEL/CentOS 7.x. This is not related to the PCoIP subsystem.

Workaround

If possible, upgrade to a newer operating system that comes with a newer kernel.

Tooltips don't show with Wacom stylus | 74256

In some applications the tooltips or hover text doesn't show when hovering the stylus over a control.

Workaround

The cause of this problem is that the default sensitivity of the Wacom stylus requires the user to hold their hand exceptionally still to trigger mouse hover text. One workaround is to use the mouse when you want to see the hover text.
Another option is to decrease the sensitivity of the stylus to suppress small movements. The default setting is to suppress anything smaller than 2. Increasing this to 30 will allow a typical user to hold the pen still enough to see the hover text. This can be done by the following command:

xsetwacom set "Wacom Intuos Pro S Pen stylus" suppress 30

Wacom tablet in mouse mode does not map cursor position correctly with Cloud Access Software | 72799

When using Cloud Access Software with Zero Client firmware 6.0 or lower the Wacom tablet cannot be locally terminated with full functionality.  The tablet will operate in mouse mode, with cursor mapping that is difficult to control and a lack of pressure sensitivity.

Workaround

Configure the Wacom tablet to be USB bridged on the zero client.

Wacom Cintiq display cursor offset | 72044

Using the Wacom Cintiq display with the tablet mapped to the entire desktop when used with more than one monitor results in an offset cursor.

Workaround

On multi-monitor workstations the tablet is mapped to the entire desktop by default. If a tablet is mapped to a single display on a multi-monitor workstation, configure both the zero client tablet mapping setting and the host tablet mapping setting. Use the Zero client OSD User Setting > Tablet Mapping screen to map the tablet to a single display. Change the host tablet mapping setting by configuring the xsetwacom MapToOutput setting. The local and remote cursors will not be in sync if the zero client and host settings are not configured properly.

Wacom local termination does not work with Wacom tablet PTH-451 | 72025

Wacom local termination does not work with Wacom tablet PTH-451

Workaround

Enable the USB permissions on the Zero Client to bridge the Wacom device. More information can be found in the Zero Client firmware Administrators' Guide. 

New RHEL version on Azure not yet supported for Graphics Agent | 71346

On Azure the NVIDIA driver only works if Linux Integration Services (LIS) is installed. When a new kernel comes out, it takes several days for Microsoft to release an LIS update to support the new kernel version. There is also delayed support for new RHEL minor releases (e.g. RHEL 7.5 is not yet supported). In order for the PCoIP Graphics Agent to work in Azure on RHEL or CentOS, the kernel must be locked down to a version which is known to be supported by both the NVIDIA driver and LIS.

Workaround

Below is a script that will install a known working kernel version, ensure it is the default booted kernel and that updates will not change the default kernel or remove the working version. It should be run as root.

#!/bin/sh

KERNEL_VERSION=3.10.0-693.21.1.el7

# ensure the default is set to the saved entry
sed -i 's/GRUB_DEFAULT=.*/GRUB_DEFAULT=saved/' /etc/default/grub

# make sure installing a new kernel package does not change the saved entry
sed -i 's/UPDATEDEFAULT=.*/UPDATEDEFAULT=no/' /etc/sysconfig/kernel

# install kernel/kernel-devel for the latest known working kernel version
yum install -y kernel-${KERNEL_VERSION} kernel-devel-${KERNEL_VERSION}

# set the installonly attribute to keep so that installing new kernels does not remove our known working kernel
yumdb set installonly keep kernel-${KERNEL_VERSION}

# find the name of the kernel we just installed in the grub config
GRUB_KERNEL_NAME="$(awk -F\' /^menuentry/{print\$2} /etc/grub2.cfg | grep ${KERNEL_VERSION} | grep -vi rescue)"

# set the grub default
eval grub2-set-default \"${GRUB_KERNEL_NAME}\"

# regenerate the grub config
grub2-mkconfig -o /boot/grub2/grub.cfg

Double cursors shown when MapToOutput is used to map a Wacom tablet | 71125

When using MapToOutput to map the Wacom tablet to something other than all displays, a duplicate and offset-ed cursor is shown, making stylus input very difficult to use.

Workaround

In order to use MapToOutput to map the Wacom tablet to a particular display, one must set the tablet mapping in the Zero Client OSD. From User Settings -> Tablet, use the stylus to select the corresponding display. Click OK to save the setting.

Ubuntu kernel on AWS EC2, Microsoft Azure, and Google Cloud Platform does not support Wacom tablets | 71110

Wacom tablets on Ubuntu with local termination from the clients when hosted on AWS, Microsoft Azure, or Google Cloud Platform fail to detect the device properly, preventing pressure sensitivity and other advanced features from working.

Workaround

Remove the Microsoft Azure, AWS, or Google Cloud kernel and install a generic one.

Steps:

  1. Check that current packages are installed:

    sudo dpkg -l "usb"
sudo dpkg -l "linux-image"
sudo dpkg -l "linux-head"

  2. Remove Azure or AWS specific kernel packages:

    • Azure:

      sudo apt remove linux-image-azure linux-image-X.X.X-X-azure
sudo apt remove linux-headers-X.X.X-X-azure

    • AWS:

      sudo apt remove linux-image-aws linux-image-X.X.X-X-aws
sudo apt remove linux-headers-X.X.X-X-aws

    • GCP:

      sudo apt remove linux-image-gcp linux-image-X.X.X-X-gcp
sudo apt remove linux-headers-X.X.X-X-gcp

  3. Install generic kernel packages:

    sudo apt install linux-image-generic
sudo apt install linux-headers-generic

  4. Reboot VM

  5. Install USB package:

    sudo apt install --reinstall usb-vhci-dkms

  6. Install PCoIP agent and Wacom driver

  7. Reboot VM

  8. To verify, launch a PCoIP session:

    sudo ll /dev/uhid
sudo lsmod |grep -i usb
sudo lsmod |grep -i wacom

Session start fails when using Host-Based Access Control if there is no rule for the pcoip-session PAM service | 68189

When authenticating against a RHEL IdM server where HBAC is in use and the allow_all rule is disabled, PCoIP sessions will fail to launch with "Error: 6405" due to users not being permitted to access the pcoip-session PAM service.

If this issue is being encountered, a log similar to this

[sssd[be[<domain>]]] [ipa_pam_access_handler_done] (0x0020): No HBAC rules find, denying access

can be seen in /var/log/sssd/sssd_<domain>.log when the SSSD debug level is set to 10 for the domain.

Workaround

Add a HBAC service for the pcoip-session PAM service and any necessary HBAC rules to allow users to connect via PCoIP.

Further information on HBAC: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/configuring-host-access

Timezone redirection may not work on RHEL | 67723

Timezone redirection from client to host may not reflect in the user session on RHEL.

Workaround

Manually set timezone on the host Virtual Machine.

PCoIP Agent failures due to license trusted storage corruption | 66726

It is possible for the agent's trusted storage to become corrupted in certain unknown circumstances. This corruption will result in the agent failing to start.

Workaround

  1. Delete the contents of C:\ProgramData\Teradici\PCoIPAgent\licensing\5 in Windows, or /var/lib/pcoip-agent/licensing/5 (requires root permissions) in Linux

  2. Restart the appropriate agent service (PCoIP Graphics Agent or PCoIP Standard Agent on Windows, or pcoip-agent on Linux).

  3. If using Teradici Cloud Licensing (not using a local license server), re-register the host.

PCoIP validate license reports unsupported version of Trusted Storage | 66075

When executing pcoip-validate-license on either Windows or Linux an error is reported stating that 

This version of trusted storage is not supported.
Workaround

  1. Delete the contents of C:\ProgramData\Teradici\PCoIPAgent\licensing\5 in Windows, or /var/lib/pcoip-agent/licensing/5 (requires root permissions) in Linux

  2. Restart the appropriate agent service (PCoIP Graphics Agent or PCoIP Standard Agent on Windows, or pcoip-agent on Linux)

  3. If using Teradici Cloud Licensing (not using a local license server), re-register the host.

Video playback performance problems on Ubuntu | 64876

Video playback on Ubuntu Linux systems using Unity can result in poor video playback.

Workaround

Unity is not supported with the PCoIP Linux Agent. Instead, use kubuntu-desktop.

Session establishment may fail when more than one monitor is present | 57936

Session establishment may fail with vGPU profiles utilizing 512 Mbytes of frame buffer when more than one monitor is present.

Workaround

Reduce the number of monitors, or change the vGPU profile to increase the frame buffer memory.

Rotation of a 1680x1050 display will fail | 55894

A PCoIP session will not be established when a 1680x1050 (or any resolution that has a height that is not a multiple of 4) display is rotated.

Workaround

Do not rotate the monitor.

No audio with Linux agent when pulseaudio is run as a system daemon | 50710

There is no audio output when pulseaudio is run as a system daemon.

Workaround

Switch the daemon to run in per-user mode, which is the default.

Black screens when using NVIDIA drivers from R367 branch with K Series cards on RHEL 7.2 | 50038

Black screens occur when using NVIDIA drivers from R367 branch with K Series cards on RHEL 7.2.

Workaround

NVIDIA driver 367.* for Linux Ubuntu or RHEL 7.2 will require an update to the hypervisor's VBIOS to the following versions: GRID K1: 80.07.AF.00.00 or higher GRID K2: 80:04:BA:00.00 or higher

User gets prompted for credentials at lock screen | 45208

If a user enables the Linux lock screen, they will be required to enter their credentials twice when reconnecting their PCoIP session: once to connect to the desktop, second to unlock the screen.

Too many taskbars created on first login to KDE | 22062

On the very first login (when the .kde directory gets populated), four taskbars are created. With a single monitor, all four will collapse on top of each other on the one display.

Workaround

Manually delete the undesired taskbars.