Arch Linux User Repository

There is a new workspace client that supports WSP. The release targeting focal supports both PCoIP and WSP and is currently at version 2024.0.4707. The release targeting jammy supports WSP only and is currently at version 2024.0.4661.

4.7.0.4312 does seem to be the latest version published on the Workspaces website https://clients.amazonworkspaces.com/linux-install

I'm getting OLD_CLIENT_VERSION too. I really hope that the maintainer will have some free time to update this as I don't know how to do it.

Hello,

I am getting a "OLD_CLIENT_VERSION" error when trying to login. I have the most recent version of the package installed. Any ideas?

[ERR] WorkSpacesClient.Common.UseCases.CommonGateways.WsBroker.PerformResourceAction.AllocateResourceResponse Error. Code: OLD_CLIENT_VERSION; Message: Client version is too old.; Type: com.amazonaws.wsbrokerservice#InvalidInputException

@thew: thanks, this sounds promising. There might be a way to spoof the lsb-release using the env variable LSB_OS_RELEASE.

It can be pointed to a different lsb_release file. Maybe its respected by the workspace client. Haven't had the time to try this yet.

If this happens to work, we could just ship the custom lsb_release file with this package

I was able to get past the:

Title: ERROR_TYPE_SESSION_PROVISION

Code: ERR_PCOIP_UNSUPPORTED_ON_PLATFORM

By editing /etc/lsb-release and applying the following so the workspaceclient binary would play along:

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=20.04

DISTRIB_CODENAME=jammy

DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS"

Hello,

I'm working on getting the new focal 2023.x release to run on arch so can use both old PCoIP and new WSP protocols. But, the new .deb files have a different file structure and as of now I wasn't able to get PCoIP to work yet.

I get an error saying to install the client on Ubuntu 20 when I try to connect.

Title: ERROR_TYPE_SESSION_PROVISION
Code: ERR_PCOIP_UNSUPPORTED_ON_PLATFORM

I assume, that the client tries to find the pcoip library but isn't able to find it or it doesn't work together with shared lib versions on arch. Log isn't helpful unfortunately.

I’ll keep trying to find a fix in the next few days.
If anyone figures it out, please share a diff or create a PR at https://github.com/jthomaschewski/pkgbuilds.

Note that the current AUR release still includes the latest version from the official deb-repository, aligning with other platforms like Flatpak.

The current AUR release does still contain the latest version of the official deb-repository which is the same version on flatpak and other platforms.
It's not deprecated/broken - just doesn't support WSP.

Posting in case others hit this - after a recent round of system package updates, my Workspaces login page no longer showed text login boxes so I was unable to login; the registration code page before that was OK, and I tried clearing out my local Workspaces homedir config files to no avail. Mousing over the window showed a presence text widgets due to the cursor changing, but I wasn't able to click/type.

I believe the error seen is related to the recent bug report in https://bugs.webkit.org/show_bug.cgi?id=261874 , and the workaround there (setting environment variable WEBKIT_DISABLE_DMABUF_RENDERER=1) worked for me. Similar to other environment variable fixes, this can be prepended into the desktop shortcut Exec line (e.g., Exec=WEBKIT_DISABLE_DMABUF_RENDERER=1 /usr/share/amazon-workspaces/workspacesclient %u)

The error messages on the console when loading the login page were:

[~]$ amazon-workspaces 
src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)

Failed to create GBM buffer of size 370x341: Invalid argument
src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)

Failed to create GBM buffer of size 370x341: Invalid argument
src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)

Failed to create GBM buffer of size 370x341: Invalid argument
Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1

I am using an older version of the AUR package (4.5.0.2006-4) as I am affected by a (more minor) client bug in newer versions, however, I similar behavior on the current AUR package version, as well.

Whatever is easily doable that gives us the latest build would be much appreciated. Jobs depend on this software.