Update to latest client about com.amazon.workspaces

[bbhtt]

#52 is a "working" build but network doesn't work, I'm not sure why. I suspect it could be due to the libsoup2.4/libsoup3 mixing.

Help appreciated in figuring that out. Logs don't show much other than "install glib-networking" but that is already in the runtime.

[bbhtt]

The beta branch is a leftover, and amazon deletes old debs so it is expected that it can't be installed.

The new version does not work #52 (comment), anyone is welcome to figure out/fix the issue.

If the amazon deletes the deb of the current version and we can't update to the new non pcoip version the package will be retired.

I can't reupload or archive a version: https://clients.amazonworkspaces.com/app-terms.html

You may not, and you will not encourage, assist or authorize any other person to, (b)... distribute, ... the Application

This Flatpak package specifically uses extra-data so that the deb gets downloaded on each user's machine and avoid redistribution. Reuploading/archiving a copy would break that clause.

[anibyl]

Amazon WorkSpaces has a web app: https://webclient.amazonworkspaces.com/

Maybe this will help people who are unable to use the new client, e.g. those who use an RPM-based distro.

[bbhtt]

I'll add it to the flathub-beta repository if successful. The stable will continue to have 'classic` workspace.

They also changed the app-id of the new client... so it is a 'new' client.

[bbhtt]

I didn't manage to fix the following issue: (the program right now crashes due to this)

Failed to load /org/gtk/libgtk/icons/16x16/status/image-missing.png: Unrecognized image file format (gdk-pixbuf-error-quark, 3)

Looking online https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/159#note_1125929 the gtk maintainers suggest reloading the loaders.cache, but

a) that's not possible in a flatpak because it is in /usr and that comes from the runtime so it is mounted read-only the app is installed to /app/extra
b) generating manually does not solve the issue.

It seems either the program is doing something weird, or they are shipping too old libraries that is incompatible the current runtime.

[bbhtt]

Ok, fixed that issue by this hack export GDK_PIXBUF_MODULE_FILE=/app/workspacesclient/usr/lib/x86_64-linux-gnu/workspacesclient/dcv/gdk-pixbuf-2.0/2.10.0/loaders.cache

The deb has this:

export LD_LIBRARY_PATH="/app/workspacesclient/usr/lib/x86_64-linux-gnu/workspacesclient/dcv:${LD_LIBRARY_PATH}"

which I'm also doing

But it can't find libraries the in /usr/lib (from the runtime) at all. Thus either crashes or has no network.

If I had to guess it seems to be not compatible to the idea that libraries inside a flatpak come from two different locations (3 counting the ones it ships with)

Also, for some weird reason it ships with libsoup-3.0.so.0 inside the deb yet depends on webkit2gtk-4.0 which links against libsoup-2.4 and the two libsoup versions are incompatible.

[compuguy]

@k4n30 There are still plenty of end users using PCoIP so I wouldn't use that version. I think the best path forward is to use the 20.04 client for now @bbhtt if it doesn't have the issues with glib-networking like #52 had. The deployments I'm working with are still using PCoIP.
Source deb: https://d3nt0h4h6pmmc4.cloudfront.net/new_workspacesclient_focal_amd64.deb

Edit: Looks like at least on 23.10 you can't connect to a PCoIP session with the latest 20.04 client. Unless there's a way to trick the Workspaces client to think its on 20.04, I don't think it will be an option here....

[dylanmtaylor]

The current client version is very dated and does not support WSP workspaces which means that Ubuntu VDIs are not streamable at all. As Amazon is moving all new Windows and Ubuntu workspaces to WSP, we need to go to the new version for this flatpak to be usable at all.

[compuguy]

The current client version is very dated and does not support WSP workspaces which means that Ubuntu VDIs are not streamable at all. As Amazon is moving all new Windows and Ubuntu workspaces to WSP, we need to go to the new version for this flatpak to be usable at all.

Agreed. On the flip side, the client I work with hasn't transitioned over to WSP workstations and is still using PCOIP. That puts me in a bizarre rock in a hard place situation. I have a personal workspace that's WSP, but the client I work with uses PCOIP...

[anibyl]

When trying to install the beta, it fails:

$ flatpak install flathub-beta com.amazon.Workspaces
...
error: Failed to install com.amazon.Workspaces: While downloading https://d3nt0h4h6pmmc4.cloudfront.net/ubuntu/dists/focal/main/binary-amd64/workspacesclient_4.6.0.4187_amd64.deb: Server returned status 403

Unfortunately, I cannot use the stable version anymore, perhaps because my workspace was reinstalled and it uses a new protocol.

[compuguy]

The beta branch is a leftover, and amazon deletes old debs so it is expected that it can't be installed.

The new version does not work #52 (comment), anyone is welcome to figure out/fix the issue.

If the amazon deletes the deb of the current version and we can't update to the new non pcoip version the package will be retired.

I can't reupload or archive a version: https://clients.amazonworkspaces.com/app-terms.html

You may not, and you will not encourage, assist or authorize any other person to, (b)... distribute, ... the Application

This Flatpak package specifically uses extra-data so that the deb gets downloaded on each user's machine and avoid redistribution. Reuploading/archiving a copy would break that clause.

Yeah I don't get that one clause. I'm pretty sure there are (unnamed) companies and government agencies who distribute it internally. I'm not a lawyer but the Eula doesn't seem to have a carve out for internal distribution?

Anyway, the last time I tried getting either build working in a flatpak in #63 and #62 it just ended in frustration. 😩

[compuguy]

Amazon WorkSpaces has a web app: https://webclient.amazonworkspaces.com/

Maybe this will help people who are unable to use the new client, e.g. those who use an RPM-based distro.

As long as the workspaces tenant has the webclient enabled, yes it is an option. Unfortunately the tenants I use do not have this option enabled, so it doesn't work in my circumstance.

Side note: Apparently the latest 22.04 workspace client doesn't install on 24.04 via repo for some strange reason. Fun times! 🙄