Package Details: vmware-horizon-client 2406-2

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.124421
First Submitted: 2015-01-08 15:17 (UTC)
Last Updated: 2024-08-20 07:04 (UTC)

Dependencies (25)

Sources (5)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 18 Next › Last »

eworm commented on 2022-03-15 15:10 (UTC)

VMware just released a fixed version, I already pushed the changes. Go and get it!

eworm commented on 2022-03-08 13:53 (UTC)

I have a non-public test release (2111.1 / 8.4.1 / build 53939787) from VMware that is said to fix the keyboard issue. To date I could not proof any different... So stay tuned for the next release!

nihalani commented on 2022-02-18 20:48 (UTC)

@KorvinSilver. Can you try adding the argument --no-sandbox to the .desktop file for VMWare Client? I had a similar issue with another application and this may serve as a stop gab solution until a more permanent one is found.

eworm commented on 2022-02-18 09:06 (UTC)

I guess that's a new security feature from KDE/Plasma, where all launched applications are sandboxed in a systemd service. Looks like this breaks the horizon client. I do not have KDE/Plasma here, so no idea what breaks.

KorvinSilver commented on 2022-02-18 08:04 (UTC) (edited on 2022-02-18 08:07 (UTC) by KorvinSilver)

I updated my system and after reboot vmware-view won't run anymore unless I start it from the terminal. I'm using KDE/Plasma and if I click on its icon, KDE shows the cursor animation for the launch for a second then nothing happens. If I run it from terminal or set the shortcut settings to include run in terminal, it works. journalctl shows this only at the time:

Feb 18 08:46:31 atsuko plasmashell[1466]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:366: Unable to assign [undefined] to QString
Feb 18 08:46:31 atsuko systemd[1026]: Started VMware Horizon Client.
Feb 18 08:46:31 atsuko plasmashell[1466]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:366: Unable to assign [undefined] to QString
Feb 18 08:46:31 atsuko kwin_x11[1108]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 62967, resource id: 52429075, major code: 18 (ChangeProperty), minor code: 0
Feb 18 08:46:31 atsuko kwin_x11[1108]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 63187, resource id: 52429076, major code: 18 (ChangeProperty), minor code: 0

So basically systemd says it's started but somehow it closes or crashes without a trace I could find. The other lines show up with everything else I start like this so unsure if they mean anything here. The exact same thing happens with nbtexplorer-bin by the way also from the AUR. No idea what that means or even what could be responsible. I have other things installed from AUR but everything else works properly. Also if I start it from terminal, there's no systemd message for it in the log.

kodur commented on 2022-01-26 20:29 (UTC)

Unable to get USB to initialize with VMware Horizon Client Version 2111 Build 8.4.0 (build-18957622).

2022-01-26 15:25:13.741-05:00: vmware-view 3233| CdkViewUsbCbFunc: callback called, reason=VIEWUSB_CB_ERROR, desktopHandle=0x5608cd452160, msgId=213, msgString="IDS_DROPDOWN_DEVICES_NOT_AVAILABLE" 2022-01-26 15:25:13.741-05:00: vmware-view 3233| CdkViewUsbCbFunc: Viewusblib callback called, open channel failed, desktopHandle=0x5608cd452160, usbAvailable=0.

eworm commented on 2022-01-25 12:42 (UTC)

Others are suffering the same issue with stuck keys: https://communities.vmware.com/t5/Horizon-for-Linux/Horizon-Client-for-Linux-fouls-key-repeating-permanently/m-p/2835084

Please post there and/or open an official support request if possible.

eworm commented on 2022-01-17 14:59 (UTC)

Added packages:

  • vmware-horizon-html5mmr
  • vmware-horizon-teams-optimization

Please test...

Anybody had success fixing the stuck keys issue?

sotix commented on 2022-01-06 07:04 (UTC) (edited on 2022-01-06 08:05 (UTC) by sotix)

@fordprefect Thanks for replying.

I did use git clone and makepkg beforehand. Now that the bundle didn't work I also tried

makepkg -sri

but that results in:

warning: cannot resolve "vmware-keymaps", a dependency of "vmware-horizon-client"
warning: cannot resolve "vmware-keymaps", a dependency of "vmware-horizon-client"
warning: cannot resolve "vmware-horizon-client", a dependency of "vmware-horizon-integrated-printing"
warning: cannot resolve "vmware-keymaps", a dependency of "vmware-horizon-client"
warning: cannot resolve "vmware-horizon-client", a dependency of "vmware-horizon-mmr"
warning: cannot resolve "vmware-keymaps", a dependency of "vmware-horizon-client"
warning: cannot resolve "vmware-horizon-client", a dependency of "vmware-horizon-rtav"
warning: cannot resolve "vmware-keymaps", a dependency of "vmware-horizon-client"
warning: cannot resolve "vmware-horizon-client", a dependency of "vmware-horizon-smartcard"
warning: cannot resolve "vmware-keymaps", a dependency of "vmware-horizon-client"
warning: cannot resolve "vmware-horizon-client", a dependency of "vmware-horizon-tsdr"
warning: cannot resolve "vmware-keymaps", a dependency of "vmware-horizon-client"
warning: cannot resolve "vmware-horizon-client", a dependency of "vmware-horizon-usb"
:: The following packages cannot be upgraded due to unresolvable dependencies:
      vmware-horizon-client  vmware-horizon-integrated-printing  vmware-horizon-mmr  vmware-horizon-rtav
      vmware-horizon-smartcard  vmware-horizon-tsdr  vmware-horizon-usb

Am I on the wrong track?

EDIT: ok I got it after carefully reading the above error: I had to install vmware-keymaps from aur, this one: https://aur.archlinux.org/packages/vmware-keymaps/

now it works

fordprefect commented on 2022-01-06 06:56 (UTC)

@Sotix: Hello and welcome. You are missing important things here, you are not using the AUR package, but the upstream installer. A good start is the Arch wiki (wiki.archlinux.org), search for AUR, makepkg, pacman, etc and understand those. That will give you an idea how arch works and what the AUR is about.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 18 Next › Last »