Inuvika OVD EDC client?

English Applications
,
1

Hi

Has anyone been able to run the Inuvika OVD Enterprise Desktop Client successfully on OpenSUSE Tumbleweed (KDE Plasma, Wayland)?

The requirements for the Linux-version are stated as below, so I presume OpenSUSE isn’t officially supported.

Linux Desktop (64-bit):
Ubuntu 14.04 and higher.
Red Hat Enterprise Linux 7 and higher.

I tried the same client also in Linux Mint (which is based on Ubuntu) and there it runs fine.
Naturally the web browser version runs also in OpenSUSE but it has too many restrictions and missing features.

If I start the client from the terminal:

ovd-edc

it states this as it starts the client:

[2026-9-3 00:33:11:144] INFO: OVD EDC version 3.5.1.8359
qt.qpa.plugin: Could not find the Qt platform plugin “wayland” in “”

If I try to connect with the client, it gives an error “Unable to reach the Session Manager” as soon as I click the Connect-button.

The log fine says this when trying to connect:

cat ~/.config/ovd/client/ovd-edc.log

[2026-9-3 00:28:17:069] INFO: QT 6.9.3 User Interface
[2026-9-3 00:28:17:132] ERROR: Curl error (27): Out of memory
[2026-9-3 00:28:30:232] ERROR: Curl error (27): Out of memory
[2026-9-3 00:28:44:359] INFO: Progress: Inuvika Inc - Start loading session : -1 %
[2026-9-3 00:28:44:371] INFO: Progress: - : 10 %
[2026-9-3 00:28:44:394] ERROR: Curl error (27): Out of memory
[2026-9-3 00:28:44:394] INFO: Hide Progress

2

Try QT_QPA_PLATFORM=wayland-egl ovd-edc

3

The clients fails to even start now. This is the error:

QT_QPA_PLATFORM=wayland-egl ovd-edc

[2026-9-3 18:33:46:704] INFO: OVD EDC version 3.5.1.8359
qt.qpa.plugin: Could not find the Qt platform plugin “wayland-egl” in “”
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

.local/bin/ovd-edc: line 25: 4052 Aborted (core dumped) “${SCRIPT}/ovd-edc” “$@”

I will try if it starts with IceVM or x11 if it runs with them and it is a Wayland issue, but I think I tried X11 before without much success…
The client seems to run on Linux Mint XFCE which to my recollection is X11.

4

Nah, Plasma X11 nor IceVM made no change, same problems.

5

So just try wayland, or xcb there are other permiations you can try…

6

How do I find what different options there are that I could try out, and is there a list of their meanings, e.g. what is the difference between xbc, wayland, wayland-egl etc.?

7

There are options at the login screen

8

That I don’t know, wayland should be the default plugin and installed, xcb is X11.

On the other distributions, what desktop environment esp env | grep QPA

9

@gogalthorp we are discussing QT plugins, not login options. :wink:

10

Yes but the OP wasiasking where he could change it

11

Sorry if I wasn’t clear, but I asled how to find the list of possible options for QT_QPA_PLATFORM=(something) that can be used when launching ovd-edc.

I know where to select at the boot screen whether to use Wayland, X11 or IceVM. I was suspecting this is some kind of Waylland issue but the problem persists even if I log in with X11 or IceVM so now I am unsure.

Anyway, I was hoping some other user might have tried to use OVD ECD on OpenSUSE and might have some tips, but I didn’t find much with Google either.
Unfortunately the company (Inuvika) does not have any user forum. I might still ask their support but let’s see if they dismiss it with “sorry we support only Ubuntu and RHEL” as those are the only Linux distros mentioned in their support material for the Linux client version.

The client does indeed seem to work fine on e.g. Linux Mint XFCE (which is based on Ubuntu). Maybe there was some hiccup there as well like I was missing some library and installing it manually fixed the client.

If I find a solution or a definite “sorry no can do” answer to this soon, I’ll update it to this discussion, in case the thread hasn’t closed already.

As said, the web browser version of OVD works ok in OpenSUSE too, but it is inferior to the client version (can’t control UNICDDE or many other options missing, overall it is less responsive and the output seems a bit blurry. The web browser version is more like a stopgap solution in case you don’t have the client available.

12

XFCE is X11 only, perhaps they only support X11 and not Wayland. That’s probably the question you need to ask…

13

Going over this thread, it looks like not only do you need to be using an X11 environment (or Plasma Wayland with QT_QPA_PLATFORM=xcb ovd-edc) but also the next hurdle are those curl errors. It’s likely that its core cryptographic are newer than what the Inuvika client expects. (That could be why using Ubuntu or Mint succeeds.)

For example, on SR (essentially same as TW)…

~> update-crypto-policies --show
DEFAULT
~> curl --version
curl 8.21.0 (x86_64-suse-linux-gnu) libcurl/8.21.0 OpenSSL/3.5.3 zlib/1.3.1 brotli/1.2.0 zstd/1.5.7 libidn2/2.3.8 libpsl/0.23.3 libssh/0.11.5/openssl/zlib nghttp2/1.70.0 ngtcp2/1.24.0 nghttp3/1.18.0 mit-krb5/1.22.2 OpenLDAP/2.6.13
Release-Date: 2026-06-24
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt mqtts pop3 pop3s rtsp scp sftp smtp smtps telnet tftp ws wss
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTP3 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd

You could try

sudo update-crypto-policies --set LEGACY

then try running the application again. Any different?

14

Thanks, you might be on the right track.
Here is the summary what I’ve tested so far:

sudo update-crypto-policies --set LEGACY
reboot
update-crypto-policies --show
LEGACY

In X11 Plasma, these two don’t show any “qt.qpa.plugin: Could not find the Qt platform plugin “XXXXXX” in “”” errors:
ovd-edc
QT_QPA_PLATFORM=xcb ovd-edc

In Wayland Plasma only this doesn’t give the qt.qpa.plugin error:
QT_QPA_PLATFORM=xcb ovd-edc

“ovd-edc” alone gives the plugin error (Could not find the Qt platform plugin “wayland” in “”), but the client still runs.

This doesn’t work at all in Wayland but the client crashes:

QT_QPA_PLATFORM=wayland-egl ovd-edc

qt.qpa.plugin: Could not find the Qt platform plugin “wayland-egl” in “”
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: xcb.
/home/username/.local/bin/ovd-edc: line 25: 6201 Aborted (core dumped) “${SCRIPT}/ovd-edc” “$@”

However, in all above cases both in X11 and Wayland, the client still fails to connect and there are still the “Curl error (27): Out of memory”-errors in the ovd log, even though crypto-policies was set to legacy.

I will still check if I see any curl memory errors or anything similar in the Mint system, to get an idea how it should behave and report.

15

I checked in Linux Mint and there I don’t get those curl out of memory errors.
Since the problems happen in OpenSUSE also in X11 Plasma, I’m inclined to believe this is not a Wayland issue but indeed something related to the connections like TLS handshaking or whatever, like you suggested.
The error that the client gives points to not being able to reach the target server.

16

Probably as far as we can take this here. Maybe Leap 16 would be worth a shot?

Since the same client works on Mint but produces Curl error (27) on openSUSE, including under X11 and with the crypto policy set to LEGACY, I’d probably take this to the application developers at this point. Share your comparative findings with them, especially with respect to curl.