I’m trying to run Stremio (
stremio-shell/DEBIAN.md at master · Stremio/stremio-shell · GitHub) on my Vero 4K+.
It’s built and installed fine but on running I get:
qt.qpa.screen: QXcbConnection: Could not connect to display :0
Could not connect to any X display
Which I understand to be because OSMC does not run a X display server? If so what is it running? Wayland? Does anyone know how I can get a QT application running?
If I recall correctly, Kodi runs under framebuffer.
I’ve made a simple addon for xwindows on osmc, but current implementation, it wont run along side kodi. The addons shutsdown kodi and starts an xserver.
check it out here:
I’ve made a small installer for a simple desktop, that runs fine on a pi2, pi3, vero2 and vero4k with the latest image installed. This in NOT an official desktop installation. The installer takes about 15 mins to install everything, with a few none vital warnings. It installs Xserver, LXDE core, Chromium, OSMC desktop background image and one Icon on the desktop, for a file manager. Finally a starting/launcher addon for kodi.
This installer, also installs a “virtual mouse & keyboard” controlled…
Interesting thanks. Does anyone know if it’s possible to run Stremio with Framebuffer directly? I’m assuming that would be more performant here?
Any possibility of OSMC offering it as an alternative to Kodi?
It looks like you’re trying to run a Qt application which uses X11. This won’t work on an OSMC installation out of the box.
Thanks for confirming. Does OSMC/Kodi on the Vero bypass display servers (
X.org/Wayland) entirely then? Or am I misunderstanding how it works?
Thanks for that link, really helpful. Have I understood right that EGLFS is something that QT as a whole is built with rather than the individual application? And if so would my steps here be roughly:
Compile QT itself on the Vero 4K+ with EGLFS
Compile Stremio, this time using the QT from step 1 rather than from debian repositories
Qt can be compiled in a way that uses EGL as a rendering backend and older versions of Qt have their own internal windowing system that use QWS which renders directly to framebuffer. QWS has a performance penalty but is lean in terms of dependencies – which is why we use it for our target installers.
I think this is beyond the scope of this forum however.