Arch Linux User Repository

The "sticky keys" issue (once CTRL is pressed on the virtual machine, it ceases to function in the parent OS) is still present for me on 2203.

@eworm great news finally, thanks for sharing! and i can confirm it finally works!

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

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!

@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.

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.

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.

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.

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.

Added packages:

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

Please test...

Anybody had success fixing the stuck keys issue?