Package Details: vmware-horizon-client 2406-4

Git Clone URL: https://aur.archlinux.org/vmware-horizon-client.git (read-only, click to copy)
Package Base: vmware-horizon-client
Description: VMware Horizon Client connect to VMware Horizon virtual desktop
Upstream URL: https://customerconnect.omnissa.com/downloads/info/slug/desktop_end_user_computing/vmware_horizon_clients/horizon_8
Licenses: custom
Conflicts: vmware-horizon-pcoip, vmware-horizon-teams-optimization, vmware-view-client, vmware-view-open-client, vmware-view-open-client-beta
Replaces: vmware-horizon-pcoip, vmware-horizon-teams-optimization
Submitter: eworm
Maintainer: eworm
Last Packager: eworm
Votes: 55
Popularity: 0.006102
First Submitted: 2015-01-08 15:17 (UTC)
Last Updated: 2025-05-05 08:25 (UTC)

Latest Comments

1 2 3 4 5 6 .. 18 Next › Last »

cosmocat commented on 2025-04-14 10:11 (UTC) (edited on 2025-04-14 10:15 (UTC) by cosmocat)

@eworm : Thank you! The omnissa-horizon-client works great on Wayland (apart from the warning message that says, 'The display server protocol you are using is not supported. It is recommended to connect with the x11 display server protocol,' but it still functions).

eworm commented on 2025-04-14 07:25 (UTC)

Yes, please.

fordprefect commented on 2025-04-14 07:00 (UTC)

@eworm: Is this package now deprecated, and users should switch to the mentioned one?

eworm commented on 2025-04-14 06:57 (UTC)

That version does not exist. Please switch to Omnissa Horizon Client: https://aur.archlinux.org/packages/omnissa-horizon-client

cosmocat commented on 2025-04-14 06:24 (UTC)

Hello, can you update this Package to latest version 2412 ? Thank you

charims commented on 2025-01-30 19:15 (UTC)

When trying to use a smart card in the UI saying something like "Access denied. No valid certificate provided."

And you have this in the log:

version `OPENSSL_3.4.0' not found

Then it turns out that you need to make a couple symlinks to get smartcards working again:

sudo ln -sf /usr/lib/libssl.so.3 /usr/lib/vmware/libssl.so.3
sudo ln -sf /usr/lib/libcrypto.so.3 /usr/lib/vmware/libcrypto.so.3

The omnissa client (who purchased horizon-view from vmware) has the same problem.

Kimloc commented on 2024-12-27 20:20 (UTC)

Client updated to version 2412 https://customerconnect.omnissa.com/downloads/info/slug/desktop_end_user_computing/omnissa_horizon_clients/8

Kimloc commented on 2024-12-10 13:53 (UTC)

This is assuming that the users are attempting to access horizon-client with a smart card

I have done testing on this issue and it appears to be something upstream within Arch. Spinning up horizon-client on other arch based distros results in horizon-client not showing PKI Validation as a Protocol Connection Certificate Checking Mode. Instead it only shows (distro dependent) Thumbprint verification or Thumbprint or PKI Verification...but not PKI Verification alone.

If a user still has Horizon-Client installed, it will still show the PKI Verfication as a phantom option that is selected, but not actually valid anymore.

Steps to reproduce: Install any Arch based distro, install vmware-horizon-client from the AUR

Steps to verify: Install horizon-client on any non-arch distro and all options appear (eg. PopOS, Kubuntu, Mint)

eworm commented on 2024-12-10 09:12 (UTC)

No idea on the smartcard issue... I do not have a setup to test this. If you find a solution let me know - I will happily apply it.

The keyboard thing sounds unrelated... Possibly caused by other updates? The only change in 2406-2 was regarding usb redirection, so... I hope your keyboard is not redirected via usb?

idiotuser commented on 2024-12-09 16:15 (UTC)

Updated to version 2406-2 and now the client disables the Meta keys on my USB keyboard. I'm no longer able to "get out" of a fullscreen session by hitting meta to bring up the local machines taskbar/task manager. The keyboard needs to be physically disconnected and plugged back in to re-enable the meta keys, as they will no longer work on local machine either.

1 2 3 4 5 6 .. 18 Next › Last »