FATAL: CApplication::Create: Unable to init windowing system

Help and Support Vero 4K / Vero 4K +
1

All of a sudden when I wanted to watch something I see a sad smiley and something seems to be looping.
When looking in the log file I see this:
19:29:23.708 T:4109415360 ERROR: AML: no rw on /sys/class/ppmgr/ppmgr_3d_mode
19:29:23.735 T:4109415360 NOTICE: InitWindowSystem: Using EGL Implementation: amlogic
19:29:23.908 T:4109415360 ERROR: EGL error in InitDisplay: 3001
19:29:23.908 T:4109415360 ERROR: InitWindowSystem: Could not create display
19:29:23.908 T:4109415360 FATAL: CApplication::Create: Unable to init windowing system

What can this be? How can I fix it asap because I can’t watch my movies/series now.

btw I didn’t update to the latest version yet and I disabled auto updating.

[EDIT] Solved! See below replies.

2

We can’t help without complete logs…

3

You are totally right! Sorry I didn’t do that yet.
Here is the complete log: http://paste.osmc.io/yuhalusubo.vhdl

Mind you I also meanwhile (before there complete logs were created) ran these 2 commands:
sudo apt-get update
sudo apt-get dist-upgrade

4

I’m mobile so haven’t looked at the logs, but you’ve probably installed Hyperion and brought in MESA libraries. This will stop the display from working correctly.

This was discussed recently so a search for MESA in the Vero section will help

1 Like
5

Checked your log. Uninstall MESA and all will work again.

6

I’m searching the forum but can’t yet find the uninstall commands.
And google is also not helping yet.

7

Probably something like sudo apt-get remove --purge libegl1-mesa. Use dpkg -l to get the correct name

1 Like
8

Thanks all for your quick response! Excellent support!

Now I’m going back to trying Hyperion :).
Hopefully @penfold42 will reply in the other topic soon.

Thanks again!

[edit] Hmmmm. Seems removing that mesa breaks my Hyperion.ng installation.
I get this “bin/hyperiond: error while loading shared libraries: libQt5Gui.so.5: cannot open shared object file: No such file or directory”.

9

how did you remove the mesa bits?
if you used dpkg to do it it might have helpfully uninstalled some of the Qt5 packages too.

The weird thing on my system is I cant find how I fixed it…
My pi3 with OSMC is my primary dev system for hyperion so it definitely needed it resolved - even with a quick hack!

I remember hacking the mediacenter script at one point to force the library search path but it looks like its now the default.

I wonder if the installation order is important for how the library search path ends up. It will have been months since qt5 was installed, but OSMC get updated monthly

EDIT: found an old post of mine on here:

This modification is currently not on my system

10

I removed it with: sudo apt-get remove --purge libegl1-mesa
So do you have an idea how I can get Hyperion.ng working again without breaking OSMC working?
Which commands to I need to run?

11

We’ll likely need sams help to retrace my old steps from the Pi on the 4K.

Grab the list of libraries that kodi.bin and hyperiond are trying to use:

ldd hyperiond

ldd kodi.bin

Reinstall the qt5 dependencies

Repeat the ldd commands above

At this point, hyperiond should work and kodi should fail again.

Post the results of the 4 ldd commands and we can take it from there

12

Ok I can do that but is there an easy way of making a backup (image) first? Or how can I quickly revert back in case I want to see a movie/serie whilst kodi is not working?
Is that by just running: sudo apt-get remove --purge libegl1-mesa you think?

I can then just repeat the steps again when you (or Sam) have another new thing to test out.

13

It might be as simple as the modification above with appropriate changes for the 4K

If kodi is working right now, can you get me the ldd of kodi.bin ?

14

Couldn’t find the kodi.bin so quickly but found it in the end in /usr/lib/kodi
Here is the output: http://paste.osmc.io/huwomahape.coffee