Release Notes
Client SDK for Linux 24.10.2
Important Notes and Requirements
-
Use of Anyware Client SDK requires a separate agreement with HP Anwyare.
-
The SDK is intended for use cases where client customizations are required and when Anyware Software Clients, PCoIP Zero Clients, and PCoIP Mobile Clients are not sufficient.
-
The SDK is intended for customers with software development skills and knowledge, as well as a sound understanding of virtualization systems.
Version 24.10.2 of the Anyware Client SDK for Linux contains bug fixes and stability enhancements.
Audio Input Did Not Connect on Linux Clients
On Anyware Client for Linux 24.10.1, the Audio Input device (Microphone) was not functional during in-session communication. This issue has now been fixed.
When Authenticated Using a Smartcard, Session Does Not Resume After Network Interruption
If a session is established using a smartcard, it may not automatically re-establish the connection after a disruption in network.
If the reconnection attempt fails, reauthenticate using the smartcard to reconnect.
SmartCard not available following session disconnect
Following the disconnection of a Anyware session that used SmartCard authentication, the card may become unavailable to use for a short period.
The SmartCard should become available to use again a short time after a session has ended, you can wait up to a minute for the card and reader to reset, or remove and re-insert the smartcard to expedite this reset.
If the card remains unavailable, try unplugging and re-plugging the smart card reader. If that does not work, restart your client host.
Caps Lock and Kana state can go out-of-sync when a Japanese keyboard is used
When a Japanese keyboard is used on the client side in a PCoIP session, the Caps Lock state can be out-of-sync on the host side if the Caps Lock key is pressed outside of the PCoIP client window.
On the client machine, set the input language to non-Japanese when a Japanese keyboard is used.
Do not press the Caps Lock key outside of the PCoIP client window when a Japanese keyboard is used.
If the Caps Lock state is out-of-sync inside a PCoIP session, disconnect and reconnect to the host.
PCoIP Client on Ubuntu 22.04 with Wayland can limit to 30 Hz for 4k displays
Remote refresh rate can be limited to 30 hz for 4k displays when connecting to a PCoIP session. This can be due to an inability for the PCoIP client to retrieve the monitor display EDID when running under Wayland on Ubuntu 22.04. This is expected as Wayland is not supported by Anyware at this time.
Disabling Wayland by editing:
sudo vi /etc/gdm3/custom.conf
to uncomment the line:
Uncomment the line below to force the login screen to use Xorg WaylandEnable=false
and reboot the client computer. Subsequent Anyware connections will be able to retrieve the EDID and will properly negotiate 60 Hz timing if the monitor is capable of that refresh rate.
Linux Keyboard - Pause/Break/Log Off and Application shortcut keys not forwarded
When connecting a Linux Anyware Client the following two keyboard short-cut keys are not forwarded to the remote session: # Pause/Break key (for standard keyboard) Pause/Break/Log Off (for Bloomberg Keyboard) # Application key
These keys will affect the local Linux OS, not the Anyware remote desktop.
This impacts any USB keyboard with these shortcut functions, including Bloomberg Keyboard.
Use alternate methods to initiate the function of these shortcut keys within the Anyware remote desktop session.
The name of network shown in Anyware Health Monitor does not change during a session
In Anyware Health Monitor, the name of network shown will not change during a session even if the actual network changes.
For example, if an ethernet cable is pulled out and the system switches to WiFi, the name of network will not change in the Anyware Health Monitor display until the session is disconnected and reconnected.
PCoIP Client in window mode can be limited to 30 fps
For high resolution displays with dimensions larger than 3840x1600 the maximum fps will be limited to 30.
To enable up to 60 fps either set the client in full screen mode or reduce the window size to dimensions less than 1600 pixels.