Hello,
I recently started to use TW KDE and try to use “Omnissa Horizon Client”. On a previous Debian installation I was able to use the “deb” version they provide. But here in TW I can’t use the “rpm” version.
Yast gives me the below error indicating “libXinerama” is missing:
I installed all of those i could find:
(I only can embed one image… but software manger says I have all the available libXininerama 1.15-1.6. installed)
But even after re-start Yast gives me the same error.
I installed VMware anyway (and it gives me errors again), but it doesn’t work at all.
I googled for some solutions and some indicate to enter some more code in terminal. but before I install random software or enter random commands, I thought I better ask first.
I’m sorry, I don’t understand what the solution is. I ran both commands. The first just gave me the rpm options. The second told me the directory doesn’t exist.
I see that Suse adds a “1” to some library names. But why? And what should I do about that? Will this a problem with all software that doesn’t come in a repository? Am I basically limited to software that is “approved” and in a repository?
I read about the (not recommended) Alien option to convert the deb file. but that may yield the same problem if Suse uses different library names.
@Lurking GUI’s can’t do everything You need to use the full path and rpm name a . means run it here, or if you cd to the directory where the rpm is and use the fullname rpm --install --nodeps Omnissa-Horizon-Client-YYMM-x.x.x-yyyyyyy.x64.rpm
This is what I entered from the Omnissa instructions:
sudo rpm -ivh Omnissa-Horizon-Client-2506-8.16.0-16536624989.x64.rpm
[sudo] password for root:
warning: Omnissa-Horizon-Client-2506-8.16.0-16536624989.x64.rpm: Header V4 RSA/SHA256 Signature, key ID 3cf8e11a: NOKEY
error: Failed dependencies:
libXinerama >= 1.1.3 is needed by omnissa-horizon-client-2506_8.16.0-16536624989.x86_64
libXrandr >= 1.5.2 is needed by omnissa-horizon-client-2506_8.16.0-16536624989.x86_64
vmware-horizon-client conflicts with omnissa-horizon-client-2506_8.16.0-16536624989.x86_64
vmware-horizon-client conflicts with (installed) omnissa-horizon-client-2506_8.16.0-16536624989.x86_64
It works. Except I’m missing those libraries. Suse has the 1 and 2 appended to libxinerama and libxrandr respectively. This is the same issue as with doing it with YaST.
How do I get the correct libraries? And why does Suse have them different?
Sorry. I should have phrased that better. It worked starting the installation. But failed due to missing libraries.
Thanks for the explanation on the library names. But what do I do?
I had (another can or worms) idea to install Wine or similar and use the Windows version of the VMWare. But I suspect this won’t be smooth either.
I was able to install it on a previous Fedora installation (also uses rpm). So I was hoping this works in Suse. Or does Suse not like rpm due to the libraries and how it names them?
Thanks, I tried that. But it tells me the the client is already installed. And it is installed, it just doesn’t work when I click on it (absolutely nothing happens).
I tried to find and remove it in Discover, but couldn’t find it.
and when I try to install with YaST, it still tells me about the missing libraries.
I read more about the deb/rpm issue. And it seems none are standardized and rpm often is optimized for RedHat. Is this a case where to software doesn’t work in Suse? In Fedora/Debian it was more or less straightforward to install and use it. And since this is proprietary software my employer uses, I can’t just find a more suitable software that is in the repository or flatpack.
I also installed Wine, but that does nothing for the .exe version. Somewhere I read about distrobox… but this all seems to make this more complex.
stephan@linux64:~/Downloads> horizon-client
/usr/lib/omnissa/horizon/bin/horizon-client: error while loading shared libraries: libclientSdkCPrimitive.so: cannot open shared object file: No such file or directory
64 bit package installing lib to /usr/lib/ instead of /usr/lib64/ as openSUSE uses, so also a Red Hat rpm Problem…