Release Notes
Standard Agent for Linux 19.11.2
Release 19.11.2 of the Standard Agent for Linux replaces and deprecates release 19.11.0. It includes the following enhancements:
-
Security fixes
It also includes the following changes from 19.11.0:
-
PCoIP Ultra with CPU acceleration enabled shows increased video playback quality.
-
Added support for local termination of additional Wacom tablets:
- Wacom Cintiq 22HD
- Wacom Cintiq 22HDT
- Wacom Cintiq 24 Pro P
- Wacom Cintiq 24 Pro PT
Local termination with these tablets also requires PCoIP Tera2 Zero Client Firmware 6.5.0 or higher.
-
You can now disable the locally-rendered cursor. This prevents double cursors in applications that render their own cursor.
-
The cursor now hides as expected during video playback.
-
Bug fixes and security enhancements.
Wacom touch key for Display Settings does not work in a PCoIP session
For Wacom Pen Displays, touch key for Display Settings does not work in PCoIP session. If user taps Wacom Display Settings touch key at the top right corner of the display, "Compatible display device not found" message would appear in Windows host and no response in Linux host.
Do not use Wacom Display Settings touch key.
Wacom Cintiq 24 Pro P cursor flashing when used with local termination
The cursor mapping for the Wacom Cintiq 24 Pro P is incorrect and results in a cursor update flashing between the correct cursor position and the origin.
None.
gnome-shell crashes repeatedly causing failure to start a session
When first attempting to start a PCoIP session using the GNOME desktop, the gnome-shell process can crash repeatedly, causing the desktop to exit and an error code to be returned to the PCoIP client.
If the backtrace is something like the following:
#0 0x00007f0bc8dba901 in __strlen_sse2_pminub () at ../sysdeps/x86_64/multiarch/strlen-sse2-pminub.S:38
#1 0x00007f0bcb35aec2 in do_lookup (path=path@entry=0x0, size=size@entry=0x7f0bafdcda98, flags=flags@entry=0x0, data=data@entry=0x0, data_size=data_size@entry=0x0, error=error@entry=0x7f0bafdcda40, lookup_flags=G_RESOURCE_LOOKUP_FLAGS_NONE, resource=<optimized out>) at gresource.c:609
#2 0x00007f0bcb35b4fd in g_resource_get_info (resource=<optimized out>, path=path@entry=0x0, lookup_flags=lookup_flags@entry=G_RESOURCE_LOOKUP_FLAGS_NONE, size=size@entry=0x7f0bafdcda98, flags=flags@entry=0x0, error=error@entry=0x7f0bafdcda40) at gresource.c:836
#3 0x00007f0bcb35bb4d in g_resources_get_info (path=path@entry=0x0, lookup_flags=lookup_flags@entry=G_RESOURCE_LOOKUP_FLAGS_NONE, size=size@entry=0x7f0bafdcda98, flags=flags@entry=0x0, error=error@entry=0x0) at gresource.c:1241
#4 0x00007f0bc82ea8da in _gdk_pixbuf_new_from_resource_try_pixdata (resource_path=resource_path@entry=0x0) at gdk-pixbuf-io.c:1700
#5 0x00007f0bc82ea9cf in gdk_pixbuf_new_from_resource (resource_path=0x0, error=error@entry=0x40ab180) at gdk-pixbuf-io.c:1751
#6 0x00007f0bca6662eb in icon_info_ensure_scale_and_pixbuf (icon_info=0x40ab0f0 [GtkIconInfo]) at gtkicontheme.c:3912
#7 0x00007f0bca66658c in load_icon_thread (task=0x7f0ba801b410 [GTask], source_object=<optimized out>, task_data=<optimized out>, cancellable=<optimized out>) at gtkicontheme.c:4164
#8 0x00007f0bcb370cbd in g_task_thread_pool_thread (thread_data=0x7f0ba801b410, pool_data=<optimized out>) at gtask.c:1331
#9 0x00007f0bcadf0e8c in g_thread_pool_thread_proxy (data=<optimized out>) at gthreadpool.c:307
#10 0x00007f0bcadf04f0 in g_thread_proxy (data=0x232ca30) at gthread.c:784
#11 0x00007f0bc9020dd5 in start_thread (arg=0x7f0bafdce700) at pthread_create.c:307
#12 0x00007f0bc8d49ead in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
it may be due to an issue with the icon cache. Running the following commands will regenerate the icon and pixbuf loader cache, resolving the issue:
# gtk-update-icon-cache /usr/share/icons/gnome
# gdk-pixbuf-query-loaders-64 --update-cache
PCoIP session ends when using very large application window
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.
Do not stretch a window more than 4096 pixels, horizontally or vertically.
License registration fails when proxy server name resolution takes too long
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.
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
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.
If possible, upgrade to a newer operating system that comes with a newer kernel.
Wacom tablet in mouse mode does not map cursor position correctly with Cloud Access Software
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.
Configure the Wacom tablet to be USB bridged on the zero client.
Wacom Cintiq display cursor offset
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.
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
Wacom local termination does not work with Wacom tablet PTH-451
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
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.
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.
Timezone redirection may not work on RHEL
Timezone redirection from client to host may not reflect in the user session on RHEL.
Manually set timezone on the host Virtual Machine.
Changing display configuration during an active PCoIP session not supported
Changing display resolution within the VM during a PCoIP session is not supported and may cause display issues.
Set preferred display resolution at the client device.
PCoIP validate license reports unsupported version of Trusted Storage
When executing pcoip-validate-license on either Windows or Linux an error is reported stating that
This version of trusted storage is not supported.
-
Delete the contents of C:\ProgramData\Teradici\PCoIPAgent\licensing\5 in Windows, or /var/lib/pcoip-agent/licensing/5 (requires root permissions) in Linux
-
Restart the appropriate agent service (PCoIP Graphics Agent or PCoIP Standard Agent on Windows, or pcoip-agent on Linux)
-
If using Teradici Cloud Licensing (not using a local license server), re-register the host.
Video playback performance problems on Ubuntu
Video playback on Ubuntu Linux systems using Unity can result in poor video playback.
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
There is no audio output when pulseaudio is run as a system daemon.
Switch the daemon to run in per-user mode, which is the default.
Too many taskbars created on first login to KDE
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.
Manually delete the undesired taskbars.