PCoIP Standard Agent for Linux 2.15.0 Release Notes

Release Overview

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

This article provides a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.

What's New in This Release

Release 2.15 of the PCoIP Standard Agent for Linux includes the following new features:

• The configuration setting to enable pcoip statistics logging is now documented. 
• Processing updated network proxy configurations no longer requires an agent restart.
• pcoip-validate-license now reports proxy settings used for license validation (if set).
• USB bridging support has been expanded, allowing wider use of USB devices.
• The PCoIP Standard Agent for Linux now supports multiple NICs. A specific interface for PCoIP traffic can be selected via configuration if required; otherwise, the agent will automatically select an interface. No configuration is required for automatic interface selection.
• Local license server users can now use their own certificates to allow https communication between the license server and the PCoIP Standard Agent for Linux.

Important Notes and Requirements

• PCoIP Standard Agent 2.15 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 Standard Agent is available through the apt (Ubuntu) or yum (RHEL) command line utility. Refer to Installing Standard Agent for Ubuntu or Installing Standard Agent for RHEL for further information.

Related Documents and Software

• Teradici PCoIP® Standard Agent 2.15 for Linux Documentation
• Open-source and third-party components

Release History

Version	Date	Description
2.15.0	February 2019	General Availability

Compatibility 

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

Resolved Issues

None.

Known Issues

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.

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.

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:

To make it work, remove Microsoft Azure, AWS or Google Cloud specific kernel and install a generic one.

Steps:

1. Check current packages 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, then run these 3 commands:

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

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.

Changing display configuration during an active PCoIP session not supported (67560)

Changing display resolution within the VM during a PCoIP session is not supported and may cause display issues.

Workaround:

Set preferred display resolution at the client device.

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.

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.

Screen resolution reverts to 1024x768 on first connect when using KDE (48166)

When you connect to a PCoIP session after Linux has rebooted (or when you previously logged out), you will notice that the screen resolution is 1024x768. This issue only occurs after a reboot (or logout) and not subsequent PCoIP session connects.

Workaround:

Do not use KDE as Teradici believes this issue is specific to KDE. Or, if you are using a software client, resize screen to get proper screen size. If using a zero client, disconnect and reconnect PCoIP session.

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.