Package Details: omnissa-horizon-client 2512-3

Git Clone URL: https://aur.archlinux.org/omnissa-horizon-client.git (read-only, click to copy)
Package Base: omnissa-horizon-client
Description: Omnissa Horizon Client - connect to Omnissa Horizon virtual desktop
Upstream URL: https://customerconnect.omnissa.com/downloads/info/slug/virtual_desktop_and_apps/omnissa_horizon_clients/8
Licenses: custom
Conflicts: vmware-horizon-client, vmware-horizon-mmr, vmware-horizon-pcoip, vmware-horizon-rtav, vmware-horizon-smartcard, vmware-horizon-teams-optimization, vmware-horizon-tsdr
Replaces: vmware-horizon-client, vmware-horizon-mmr, vmware-horizon-pcoip, vmware-horizon-rtav, vmware-horizon-smartcard, vmware-horizon-teams-optimization, vmware-horizon-tsdr
Submitter: eworm
Maintainer: eworm
Last Packager: eworm
Votes: 9
Popularity: 0.86
First Submitted: 2025-01-06 12:37 (UTC)
Last Updated: 2025-12-18 21:33 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

DeathByDenim commented on 2026-01-14 16:22 (UTC)

Oh, huh, it started working suddenly. It didn't when I had started my session. Weird, but thanks!!

DeathByDenim commented on 2026-01-14 13:11 (UTC)

@Nuk3 Hmm, I just tried that but it didn't work. However, I think that's because these settings are managed by my administration. Even though the turn off custom scaling button is there and I can click it, it resets right back to custom scaling after a restart.

Oh well!

Nuk3 commented on 2026-01-12 13:52 (UTC) (edited on 2026-01-12 14:25 (UTC) by Nuk3)

@DeathByDenim I had the same problem, I turned off custom scaling on remote PC, logged off, turned back on, logged off and restarted. It started dynamic scaling again.

DeathByDenim commented on 2026-01-12 12:44 (UTC)

@FirTimInsArc It works under Wayland for me (KDE). The only thing that is not working is that if I resize the window, the remote desktop doesn't resize with it and instead just shows black bars or cuts off part of it. SO, I'm always stuck with the default resolution.

FirTimInsArc commented on 2026-01-07 08:26 (UTC)

I'm having troubles getting this to work with Wayland... (It's fine on Xorg/X11). Is there plans to make this compatible with Wayland or is that more so an Omnissa issue and we have to continue to use Xorg/X11 for the time being?

frankspace commented on 2025-12-24 22:57 (UTC) (edited on 2025-12-24 22:58 (UTC) by frankspace)

@sklknn, I'm not encountering any crashes (since moving to the bundled openssl libraries), but again, I'm using the "fixed" version of libx11 from https://aur.archlinux.org/packages/libx11-mr293. I suggest first testing to see if that solves the problem instead of downgrading.

sklknn commented on 2025-12-24 22:50 (UTC)

as ic kbd crashes still there. im here to pin out that downgrading libxkbcommon and libxkbcommon-x11 to 1.11.0-1 still solves this issue, while current ver is 1.13.1-1.

jskier commented on 2025-12-22 15:25 (UTC)

Yeah, you're right. I played around with systemwide, and it will just break Arch Linux; it's too old.

You should just be able to use what is with the bundle, and it will work.

eworm commented on 2025-12-22 06:49 (UTC)

BTW, looks like we have openssl 3.0.18 here. This is the latest maintenance release from 3.0.x branch at least.

eworm commented on 2025-12-22 06:42 (UTC)

On a second thought I think I have copied the bundled library from the Ubuntu system. :-p Would have to verify... But after all it does not make a big difference - let's just keep the bundled library for now.

1 2 3 4 5 Next › Last »