Arch Linux User Repository

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

at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)

at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)

at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)

at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)

at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

Can you give details on your setup? How can I reproduce?

And does it work to just remove the packaged library, so libstdc++ from gcc-libs can be used?

After upgrading to 2309-1 when being redirected to login via chromium I get that the packaged libstdc++ (usr/lib/vmware/gcc/libstdc++.so.6) does not contain GLIBCXX_3.4.32 which is required by Chromium.

The latest version of libstdc included is 3.4.30

I am using Chromium 119.0.6045.59

I have solved the problem by doing a soft link for libstdc using the libstdc son /usr/lib

The problem message:

2306-1 install fails(Installed: 2303-1): error: failed to commit transaction (conflicting files) vmware-horizon-client: /usr/share/doc/vmware-horizon-client/patches/README.patches exists in filesystem vmware-horizon-client: /usr/share/doc/vmware-horizon-client/patches/freerdp-1.1.0-tls.patch exists in filesystem vmware-horizon-client: /usr/share/doc/vmware-horizon-client/patches/freerdp-1.1.0.patch exists in filesystem vmware-horizon-client: /usr/share/doc/vmware-horizon-client/patches/rdesktop-1.6.0-win7scard.patch exists in filesystem Errors occurred, no packages were upgraded.

Is solved installing manually the AUR package vmware-keymaps (https://aur.archlinux.org/packages/vmware-keymaps). After installing this package, the next step is to install using the regular procedure "vmware-horizon-client"

Since two weeks, the Horizon client is crashing a couple of times a day at the same time with chrome and chromium, is anyone experiencing similar behaviour?

Using the latest Manjaro, Gnome, Wayland and the latest LTS Kernel (6.1.49-1).

@Pen_Pen At my organization the same thing happened and it was related to MS implementing a different dual factor authenticator (where they post a number you enter in your Authenticator app on the phone) which broke the VMWare client as it cannot support it

In our case, my organization has a web portal from which I can launch.. it has been the only workaround so far

Hello everyone

After a while without using horizon client, I am having problems when launching the desktop. I have the server configured but when I tray to start, program crashes / closes.

I tried to unistall and install, also manual build, but I can not make it work, always same issue

Has anyome experimet this problem?

Thanks in advance

Update: I was able to get by it by resetting my LANG to en_US.UTF-8:

# localectl set-locale LANG=en_US.UTF-8
# locale -a 

C
C.UTF-8
en_US.utf8
POSIX

Original Message:

Similar to @sand7000 I am also getting an "Invalid Locale" error when trying to add a server. Same locale settings:

C
C.UTF-8
POSIX
en_US.utf8

I only found another dead-end Reddit thread, has anyone else run into this?

Update. Manual build and install worked:

makepkg
sudo rm /usr/share/doc/vmware-horizon-client/patches/
sudo pacman -U vmware-horizon-.tar.zst

Problem I mentioned happened only while using yay to automatically update vmware-horizon-client.