Release Notes
Standard Agent for Linux 25.03.1
Version 25.03.1 of the Standard Agent for Linux fixes known issues, bugs and provides stability enhancements for a better user experience and seamless support.
Previous Releases in this Version
25.03
Enhanced Security Using Smart Card Authentication
Version 25.03 of the Standard Agent for Linux introduces support for in-session smart card authentication for Linux Clients that connect to Linux agents. When this feature is enabled, session authentication will use the smart card connected to the client. Once a PCoIP session is established, smart cards will also be available for tasks such as in-session authentication and document signing.
For the purpose of enabling smartcard authentication, a new parameter called pcoip.enable_smart_card has been introduced. When enabled, this parameter allows the use of PIN-enabled smartcards for session authentication, lock screen login, document signing, and other in-session operations.
Smartcard authentication provides an added security layer, and simplifies identity management within PCoIP deployments.
For additional information about smartcard authentication, see the following topics:
Support for Capturing Hardware Cursor
Version 25.03 of the Standard Agent for Linux introduces a new behaviour of capturing hardware cursor on the host machine instead of the client machine. This behaviour can be customized, and host-side cursor capture can be disabled by using the pcoip.disable_server_rendered_cursor parameter. When set to `True`, hardware cursor capture occurs on the client side.
For more information, see the following topics:
Note:
Ubuntu 20.04 will reach end of life in April 2025. Support for this version has been removed in HP Anyware 25.03.
Session Connection no longer fails when Certificate Serial Number is 0
25.03.1 Anyware Clients and Agents will now accept a broker certificates where a certificate in the chain contains Serial Number 0 (zero). This fixes a problem where connections using these certificates would fail during session establishment.
Agent Crash on Smart Card Removal
On Linux Agent, if smart card was used to authenticate it is possible for the Anyware Agent to crash and become unresponsive if that smart card is removed while the session is active. When this occurs subsequent attempts to connect the the PCoIP agent will be unsuccessful.
Avoid removing smart card while in-session, disconnect the session using the Connection>Disconnect menu or by closing the client window. If this issue does occur, reboot the agent host to restore PCoIP Agent functionality.
Windows photo background can increase bandwidth usage
When dragging a window over a complex photographic windows background this can interfere with efficient PCoIP encoding causing more bandwidth usage and delay than necessary.
Disable the windows background by setting it to a solid color like black. Follow the session planning guide OS optimization recommendations documented here: https://anyware.hp.com/products/hp-anyware/current/documentation/session-planning-guide/application-and-os-optimizations
Linux Agent PCSCD Service Fails to Start After Accessing USB SmartCard Reader
If the correct device driver is not installed on a Linux Agent on which USB Bridging is enabled, accessing the USB Smartcard reader will result in the PCSCD Service failing to start.
Ensure that the{*}* specific driver for that smartcard reader is installed.
This solution has been verified with the SCR3310 smart card reader by installing the SCR3310 smart card reader driver.
To successfully install the SCR3310 smart card reader on RHEL 8 and RHEL 9, copy the scmccid.bundle folder to the /usr/lib64/pcsc/drivers folder by running the following command:
cp proprietary/scmccid.bundle/ /usr/lib64/pcsc/drivers -r 
{}Note{}: Other brands and models of smartcard readers and drivers have not been verified and may not function as expected over USB Bridging.
Chrome Browser Cannot Distinguish Between Mouse Clicks and Pen Inputs on Linux Agents
On Linux agents, when relative mouse is enabled, Chrome Browser treats mouse clicks as pen inputs.
When relative mouse is enabled, use another supported browser if distinguishing between mouse clicks and pen inputs is necessary.
Internal Users Cannot Generate Collaboration Invitation URLs for External Users
Internal users connected to PCoIP sessions using internal addresses cannot generate collaboration invitation URLs that external users can access, as the URLs contain internal addresses.
Use a FQDN that can be accessible by both the internal and external users. The FQDN can map to an internal address for internal users, and external address for external users.
User Might be Unable to Enter Password on the Lock Screen
When the desktop is locked, it might become unresponsive to keyboard and mouse inputs for up to a minute and an authentication error might briefly appear. This can prevent users from unlocking the desktop using their password.
After a short delay, the keyboard and mouse inputs will become responsive again. Once activity resumes, the user will be able to unlock with the password.
Resizing collaboration session window causes crash
Re-sizing the PCoIP Client window while participating in a PCoIP Ultra Collaboration session may cause the PCoIP client to crash.
Avoid re-sizing client window size while participating in a PCoIP Ultra Collaboration session.
If this occurs, re-start the collaboration session by sending a new invitation to the Guest Collaborator.
Cursor artifacts may appear if collaborator client window is resized
When the collaborator client window is resized, cursor artifacts may be seen on the collaborator client momentarily.
Once the resizing settles, the artifacts will disappear.
Collaboration Manager UI Layout incorrect on CentOS 7 and RHEL 7
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.
Collaborator may not see the remote cursor when first connected
When a guest collaborator connects to the host's session, the host's cursor may not be visible to the guest until it moves.
The host collaborator should move their cursor. This will update its position and cause the cursor to appear in the guest collaborator's client.
MATE desktop background has non-responsive regions
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.
Restart the affected MATE desktop component by running the following command in a terminal window:
killall caja
The component will automatically restart, restoring full desktop interactivity.
Soon to expire licenses can cause licensing failure for new host
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.
Wait until the following day in the timezone of the license server.
pcoip.service is not enabled on systemd multi-user target
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.
If the default target is changed to multi-user after installation of PCoIP Agent, it is possible to recover with one of the following steps:
- reset the systemd default target with the following command:
systemctl set-default graphical
- reinstall PCoIP Agent: the package executes a post-installation script that resets the default target to graphical.
Timezone redirection may not work on RHEL/CentOS hosts with SELinux enabled
When SELinux is enabled on RHEL/CentOS hosts timezone redirection may not work due to the SELinux file label being incorrect on /etc/localtime.
Run restorecon /etc/localtime as root and attempt to start another session.
First PCoIP session fails to establish on RHEL/CentOS7 with SELinux enabled and nfs mounted home directories
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.
In versions 20.04 and above:
Install the pcoip-server-nfs SELinux package as follows:
# semodule -i /usr/share/pcoip-agent/selinux/pcoip-server-nfs.pp
In versions prior to 20.04:
Create a file named pcoip-server-nfs.te with the following content:
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 };
and run the following commands to build and install it:
$ 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
PCoIP Agent and PCoIP License Server commands have the same name
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.
It is advised not to install the PCoIP License Server and PCoIP Agent on the same machine
Session fails to start when using SSSD in Linux
When using SSSD for authentication in Linux starting a PCoIP session fails with the following message in the journal:
pcoip-desktop-child[<pid>]: pam_sss(pcoip-session:account): Access denied for user <user>@<domain>: 6 (Permission denied)
and the following in the SSSD domain logs:
[sssd[be[<domain>]]] [ad_gpo_access_send] (0x0400): service pcoip-session maps to Denied
[sssd[be[<domain>]]] [ad_gpo_access_done] (0x0040): GPO-based access control failed.
In /etc/sssd/sssd.conf, add the following line to the domain section:
ad_gpo_map_permit = +pcoip-session
Example:
[domain\mydomain.com]
ad_domain = mydomain.com
...
ad_gpo_map_permit = +pcoip-session
Cursor offset and wrapping while bridging Wacom pen displays
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.
Do not bridge Wacom pen display. Use Wacom pen display in local termination mode.
Wacom touch key for Display Settings does not work in a PCoIP session
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.
Do not use Wacom Display Settings touch key.
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 is unreliable in KVM environments
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.
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.
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.