Jump to content

cparke2

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

cparke2's Achievements

  1. Understood, thank you very much for the context. Very much appreciate your (continued) efforts to inform the devs of this compatibility issue that we're facing. Thank you!
  2. Well I'm glad to see that I'm not the only person facing this issue! You don't need to be a "Linux person" to understand that programs using newer processor instructions than they are supposed to under the minimum system requirements are not going to work on machines at those minimum requirements! Frankly, this is likely a compiler flag issue with your build needed to disable the generation of these machine instructions beyond SSE2. I do wish your dev team would look into it and fix the Makefile in the next version, if not issue a patch release. In the meantime, I am now doing stupid things like X-forwarding this client app. from another computer on the network, or using QEMU to emulate the unsupported instructions. It's a great hassle for an end-user application that should be lightweight and support a wide range of low-end hardware!
  3. I've been asked by my organization to update my VMware Horizon Client to version 2306 or later, or I will soon become unable to connect; I am currently using Horizon Client version 2212.1 on Linux/Ubuntu 22.04.4 LTS (64-bit). However, when I upgrade and try to connect with this new version, the application crashes with an ILLEGAL INSTRUCTION exception. This does not happen using the Windows version of Horizon Client 2306 on the same machine, however! Further analysis reveals the illegal instruction that is causing this error is an SSE4.1 instruction (PINSRQ) which my processor does not support! It is happening in the VMware shared library /usr/lib/vmware/libudpProxyLib.so for the PCoIP component. However, the processor requirements for Linux 64-bit version of VMware Horizon Client 2303 and later is only SSE2, which my processor does support. This particular shared library does not seem very large or complicated, and does not appear to need to use the newer instructions. So this looks like a build flag error/bug in VMware Horizon Client Linux version for x64 systems that should be fixed or patched by VMware so that I and others can upgrade the software. VMware Horizon Client 2303 Crash Dump Info.txt
×
×
  • Create New...