Search Criteria
Package Details: vmware-horizon-tsdr 2406-2
Package Actions
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 - folder sharing |
Upstream URL: | https://customerconnect.omnissa.com/downloads/info/slug/desktop_end_user_computing/vmware_horizon_clients/horizon_8 |
Licenses: | custom |
Submitter: | eworm |
Maintainer: | eworm |
Last Packager: | eworm |
Votes: | 55 |
Popularity: | 0.146464 |
First Submitted: | 2015-01-08 15:17 (UTC) |
Last Updated: | 2024-08-20 07:04 (UTC) |
Dependencies (6)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- glibmm
- vmware-horizon-clientAUR
- librsvg (librsvg-gitAUR) (make)
- libxslt (libxslt-gitAUR) (make)
- patchelf (patchelf-gitAUR) (make)
Required by (1)
- vmware-horizon-client (optional)
Latest Comments
1 2 3 4 5 6 .. 18 Next › Last »
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.
xwj commented on 2024-12-09 16:12 (UTC)
I'm seeing the same behavior as @tinynibbles. I have also ensured opensc-pkcs11 library is linked in the VMware view library and confirmed the vmware-horizon-usb.service is running. I'm running the same versions as well:
Here seems to be the relevant log output from vmware-horizon-client-XXX.log:
tinynibbles commented on 2024-12-05 06:26 (UTC) (edited on 2024-12-05 06:27 (UTC) by tinynibbles)
TL/DR: Horizon client is not prompting for a smartcard selection or asking for a pin. The error message in the GUI states "Access denied. No valid certificate provided."
My VMware Horizon client is no longer recognizing my smartcard. I have verified the the smartcard reader is working with the pcsc_scan tool and I have ensured opensc-pkcs11 library is linked in the VMware view library. I also confirmed the
vmware-horizon-usb.service
is running.Frostyman commented on 2024-06-27 00:14 (UTC)
Hey,
I just finished the install of the client, usb and smartcard packages, hoping to use for work, sadly I keep running into the following issue, I believe this is why the client is not prompting me for my id card pin. if anyone know where i should look to find any further logs, or might have a solution please let me know.
Thanks!
Jun 26 19:53:17 XXXX-manjaro systemd[1]: Starting VMware Horizon USB daemon... ░░ Subject: A start job for unit vmware-horizon-usb.service has begun execution ░░ Defined-By: systemd ░░ Support: https://forum.manjaro.org/c/support ░░ ░░ A start job for unit vmware-horizon-usb.service has begun execution. ░░ ░░ The job identifier is 4018. Jun 26 19:53:17 XXXXX-manjaro systemd[1]: vmware-horizon-usb.service: Control process exited, code=exited, status=1/FAILURE ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: https://forum.manjaro.org/c/support ░░ ░░ An ExecStart= process belonging to unit vmware-horizon-usb.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 1. Jun 26 19:53:17 XXXXX-manjaro systemd[1]: vmware-horizon-usb.service: Failed with result 'exit-code'. ░░ Subject: Unit failed ░░ Defined-By: systemd ░░ Support: https://forum.manjaro.org/c/support ░░ ░░ The unit vmware-horizon-usb.service has entered the 'failed' state with result 'exit-code'. Jun 26 19:53:17 XXXXX-manjaro systemd[1]: Failed to start VMware Horizon USB daemon. ░░ Subject: A start job for unit vmware-horizon-usb.service has failed ░░ Defined-By: systemd ░░ Support: https://forum.manjaro.org/c/support ░░ ░░ A start job for unit vmware-horizon-usb.service has finished with a failure. ░░ ░░ The job identifier is 4018 and the job result is failed.
ravisagar commented on 2023-12-05 11:57 (UTC)
Hello,
I am using VMware Horizon Client Version 2309.1 Build 8.11.1 (22775487)version and I get the invalid locale error.
Here is what the log says.
2023-12-05 11:49:42.314+00:00: vmware-view 23656| OnError:69: Handling error 'invalid locale' (domain=2359(CDK_BROKER_ERROR), code=14) from task CdkSetLocaleTask. 2023-12-05 11:49:42.314+00:00: vmware-view 23656| cdk_application_on_server_fatal_error: received fatal error 'invalid locale', disconnect server and show error message.
My local is set to:
C C.utf8 POSIX en_GB.utf8
rob81 commented on 2023-11-02 11:48 (UTC)
Working well now. I am not sure what was the Vulkan thing. Worked after upgrading + reboot.
eworm commented on 2023-11-02 08:02 (UTC)
Pushed vmware-horizon-client 2309-2, that should fix the chromium / libstdc++ issue. No idea on the vulkan topic...
rob81 commented on 2023-11-01 01:12 (UTC) (edited on 2023-11-01 01:12 (UTC) by rob81)
I have arch with KDE 4 using Wayland
Before the upgrade I could access the login screen (which comes up in a chromium window), and then the remote application would launch
After upgrade to 2309-1 vmware-client would offer the server but the login screen would not display. Instead, I got the error message that /usr/lib/vmware/libstdc++.so.6 did not contain glibc3.4.32. I renamed /usr/lib/vmware/libstdc++ and did a softlink to the /usr/lib/libstdc++.so.6 library. Now the login screen opens in Chromium. I am able to log in and get the menu of the remote applications.
however, when I try to access any application, the screen momentarily freezes and then I get this error:
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
1 2 3 4 5 6 .. 18 Next › Last »