Release Notes

When the desktop is locked, it may not be responsive to any keyboard and mouse inputs for up to a minute and an authentication error may briefly appear. This can prevent users from unlocking the desktop using their password.

22.07.0 Graphics Agent with GPU offload might experience following performance issues: 

• image pixelation due to image quality dropping to very low
• Bandwidth use dropping to very low results in low session FPS

Re-sizing the PCoIP Client window while participating in a PCoIP Ultra Collaboration session may cause the PCoIP client to crash.

When the collaborator client window is resized, cursor artifacts may be seen on the collaborator client momentarily.

When running on CentOS/RHEL 7, the Collaboration Manager may have an incorrect layout.  Collaboration features still function properly. This issue will be fixed in a future release.

When PCoIP Ultra is used in Auto Offload or GPU Offload modes on Ubuntu 18.04, on Microsoft Azure or GCP instances, and with NVIDIA vGPU 13.1 drivers, the PCoIP session may drop unexpectedly when resizing the client window or toggling full screen.

When a guest collaborator connects to the host's session, the host's cursor may not be visible to the guest until it moves.

After resizing the PCoIP client window some regions of the MATE desktop may be non-interactive (i.e. the right click context menu will not show up, and icons cannot be placed in these regions). This is an issue with a MATE desktop component where resize events are missed.

killall caja

If a license server is operating in a different timezone than the PCoIP Agent and a license is still valid in the timezone of the PCoIP license server but considered expired in the timezone of the PCoIP Agent, then a PCoIP session can be denied with a licensing error.

This issue only affects hosts that do NOT have a valid license granted previously.

If you are unable to start a session with PCoIP Ultra GPU Offload or Auto Offload enabled it may be due to a lack of GPU memory. This can be verified by looking for "out of memory" in the PCoIP server log.

During installation, the PCoIP Agent service is set as the default display manager of the system. As a result, systemd only activates pcoip.service when the default target is set to graphical. Setting the default target to multi-user is not supported by the PCoIP Agent.

systemctl set-default graphical

After launching a PCoIP session RHEL/CentOS host with Cintiq 22HDT bridged, the session may get disconnected and the system becomes unresponsive.

Updating or installing the Linux Graphics Agent on some centOS and RHEL machines might result in updating of the symbol from glapiCurrent {}to glapitlsCurrent in the /lib64/{}{}libOpenGL.so{} package. PCoIP sessions will not start, and the following error will be displayed:

/usr/lib/pcoip-agent/pcoip-server: symbol lookup error: /lib64/libOpenGL.so.0: undefined symbol: _glapi_tls_Current

sudo yum install libglvnd-opengl

When initiating a PCoIP connection to a RHEL/CentOS host, with SELinux enabled and nfs mounted home directories, the first connection attempt may fail if an nfs version prior to 4.2 is being used. This is due to the pcoip-server process not having permission to read files labelled nfs_t.

# semodule -i /usr/share/pcoip-agent/selinux/pcoip-server-nfs.pp

module pcoip-server-nfs 1.0;

require {
    type pcoip_server_t;
    type nfs_t;
    class dir search;
    class file { getattr open read };
}

allow pcoip_server_t nfs_t:dir search;
allow pcoip_server_t nfs_t:file { open getattr read };

$ checkmodule -m -o pcoip-server-nfs.mod pcoip-server-nfs.te
$ semodule_package -m pcoip-server-nfs.mod -o pcoip-server-nfs.pp
$ sudo semodule -i pcoip-server-nfs.pp

When both the PCoIP Agent and PCoIP License Server are installed on the same machine, they will both try and create the command pcoip-list-licenses and pcoip-support-bundle, which causes one to overwrite the other's command. Whichever is installed or updated last will be the one that the command will map to.

NVIDIA licensing limits the size and number of displays that can be connected. This document: [https://docs.nvidia.com/grid/latest/grid-vgpu-user-guide/index.html#physical-gpu-display-resolution-handling] shows that the GPU may enforce a maximum of 1, 2, or 4 displays and may limit resolution as low as 1280×1024 for a single display.

When using Wacom pen displays like the Cintiq Pro 24 in bridged mode, the cursor will appear to be offset when using a stylus. When the stylus is close to the bottom of the display, the cursor wraps to the top of the display. 

This only affects Linux hosts.

The "Display Settings" touch key for Wacom Pen Displays does not work in a PCoIP session. Windows hosts display a "Compatible display device not found" message when the user taps the touch key. Linux hosts do not display a message.

PCoIP supports a maximum application window width of 4096 pixels.  If an application window is stretched across multiple displays with a total width or height greater than 4096, the PCoIP session will end.

After upgrading to an NVIDIA GRID 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.

sudo yum reinstall xorg-x11-server-Xorg

sudo apt install --reinstall xserver-xorg-core

Retrieval of the VM_UUID can be unreliable when running under KVM. This can cause licensing failures when attempting to validate a license or start a session.

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.

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.

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.

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.

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.

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

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.

#!/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

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.

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.

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

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

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

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

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.