Kodi no longer runs

[Chromoris]

Today I updated my Ubuntu system, rebooted, and now Kodi is no longer working.

The primary errors I got was that Kodi could no longer find libGLESv2.so.2 and libEGL.so.1:
/usr/lib/arm-linux-gnueabihf/kodi/kodi.bin: error while loading shared libraries: libGLESv2.so.2: cannot open shared object file: No such file or directory
I tried to fix that by making symlinks in the /usr/lib/arm-linux-gnueabihf to those files (they are in the mesa-egl and mali-egl subdirectories there, but that is more of a workaround than a solution).
However I then end up with the following message:
libEGL warning: DRI2: failed to open exynos (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
And kodi will not show anything on the screen (I can see that the program runs, but nothing is displayed, no screen is opened)

I've checked and reinstalled Kodi, mesa, egl and exynos packages. As far as I can see they are present. Furthermore I've deleted the .kodi directory to see if a fresh start would fix things, but it did not.
I have no idea as to the cause of these issues. Could someone advise my as to how to fix the situation and get Kodi running again?

Since it started after an update, below is the install history from apt:

Code: Select all

Start-Date: 2017-07-16  23:15:00
Commandline: apt-get upgrade
Requested-By: odroid (1000)
Upgrade: libepoxy0:armhf (1.3.1-1ubuntu0.16.04.1, 1.3.1-1ubuntu0.16.04.2)
End-Date: 2017-07-16  23:15:03

Start-Date: 2017-07-19  11:04:36
Commandline: /usr/bin/unattended-upgrade
Upgrade: apport:armhf (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python3-apport:armhf (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), apport-gtk:armhf (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10), python3-problem-report:armhf
 (2.20.1-0ubuntu2.9, 2.20.1-0ubuntu2.10)
End-Date: 2017-07-19  11:05:06

Start-Date: 2017-07-20  02:44:20
Commandline: /usr/bin/unattended-upgrade
Upgrade: libexpat1-dev:armhf (2.1.0-7ubuntu0.16.04.2, 2.1.0-7ubuntu0.16.04.3), libexpat1:armhf (2.1.0-7ubuntu0.16.04.2, 2.1.0-7ubuntu0.16.04.3)
End-Date: 2017-07-20  02:44:24

Start-Date: 2017-07-21  01:20:25
Commandline: /usr/bin/unattended-upgrade
Upgrade: libmysqlclient-dev:armhf (5.7.18-0ubuntu0.16.04.1, 5.7.19-0ubuntu0.16.04.1), mysql-common:armhf (5.7.18-0ubuntu0.16.04.1, 5.7.19-0ubuntu0.16.04.1), libmysqlclient20:armhf (5.7.18-0ubuntu0.16.04.1, 5.7.19-0ubuntu0.16.04.1)
End-Date: 2017-07-21  01:20:31

Start-Date: 2017-07-25  00:58:09
Commandline: /usr/bin/unattended-upgrade
Upgrade: linux-libc-dev:armhf (4.4.0-83.106, 4.4.0-87.110), xserver-common:armhf (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), xserver-xorg-core:armhf (2:1.18.4-0ubuntu0.2, 2:1.18.4-0ubuntu0.3), imagemagick:armhf (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickwand-6.q16-2:armhf (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick-6.q16:armhf (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2-extra:armhf (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagickcore-6.q16-2:armhf (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), imagemagick-common:armhf (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), libmagick++-6.q16-5v5:armhf (8:6.8.9.9-7ubuntu5.7, 8:6.8.9.9-7ubuntu5.8), linux-tools-common:armhf (4.4.0-83.106, 4.4.0-87.110)
End-Date: 2017-07-25  00:58:24

Start-Date: 2017-07-25  19:35:48
Commandline: apt-get upgrade
Requested-By: odroid (1000)
Upgrade: libfwup0:armhf (0.5-2ubuntu4, 0.5-2ubuntu5), mali-x11:armhf (20170224-r14p0-61e43cd-13, 20170719-r17p0-a3c89b3-15), libsystemd0:armhf (229-4ubuntu17, 229-4ubuntu19), udev:armhf (229-4ubuntu17, 229-4ubuntu19), fwupdate:armhf (0.5-2ubuntu4, 0.5-2ubuntu5), libudev1:armhf (229-4ubuntu17, 229-4ubuntu19), libudev-dev:armhf (229-4ubuntu17, 229-4ubuntu19), systemd-sysv:armhf (229-4ubuntu17, 229-4ubuntu19), libpam-systemd:armhf (229-4ubuntu17, 229-4ubuntu19), systemd:armhf (229-4ubuntu17, 229-4ubuntu19), fwupdate-signed:armhf (1.11+0.5-2ubuntu4, 1.11.1+0.5-2ubuntu5)
End-Date: 2017-07-25  19:36:32

Start-Date: 2017-07-25  23:03:47
Commandline: apt-get upgrade
Requested-By: odroid (1000)
Upgrade: ruby2.3:armhf (2.3.1-2~16.04, 2.3.1-2~16.04.2), libruby2.3:armhf (2.3.1-2~16.04, 2.3.1-2~16.04.2)
End-Date: 2017-07-25  23:03:54

Start-Date: 2017-07-25  23:06:44
Commandline: synaptic
Requested-By: odroid (1000)
Install: libcogl-gles2-20:armhf (1.22.0-2), libcogl-gst20:armhf (1.22.0-2)
End-Date: 2017-07-25  23:06:46

Start-Date: 2017-07-25  23:10:12
Commandline: synaptic
Requested-By: odroid (1000)
Reinstall: libcogl20:armhf (1.22.0-2), libgles2-mesa:armhf (12.0.6-0ubuntu0.16.04.1), libcogl-path20:armhf (1.22.0-2), libgles1-mesa:armhf (12.0.6-0ubuntu0.16.04.1), libcogl-common:armhf (1.22.0-2), libglapi-mesa:armhf (12.0.6-0ubuntu0.16.04.1), libcogl-gles2-20:armhf (1.22.0-2), libcogl-pango20:armhf (1.22.0-2), libgles2-mesa-dev:armhf (12.0.6-0ubuntu0.16.04.1), libcogl-gst20:armhf (1.22.0-2)
End-Date: 2017-07-25  23:10:16

Start-Date: 2017-07-25  23:11:46
Commandline: synaptic
Requested-By: odroid (1000)
Reinstall: kodi:armhf (17.3+hk1-ubuntu2), kodi-bin:armhf (17.3+hk1-ubuntu2), kodi-data:armhf (17.3+hk1-ubuntu2)
End-Date: 2017-07-25  23:12:09

Start-Date: 2017-07-26  00:43:52
Commandline: /usr/bin/unattended-upgrade
Upgrade: openjdk-8-jre:armhf (8u131-b11-0ubuntu1.16.04.2, 8u131-b11-2ubuntu1.16.04.2), openjdk-8-jre-headless:armhf (8u131-b11-0ubuntu1.16.04.2, 8u131-b11-2ubuntu1.16.04.2), openjdk-8-jre-jamvm:armhf (8u131-b11-0ubuntu1.16.04.2, 8u131-b11-2ubuntu1.16.04.2)
End-Date: 2017-07-26  00:44:05

[meveric]

reinstalling mesa is probably a bad idea, since it replaces the Mali driver needed to run Kodi.
please reinstall mali-x11.

[Chromoris]

reinstalled mali-x11, no luck, still getting the following error when trying to run kodi:
/usr/lib/arm-linux-gnueabihf/kodi/kodi.bin: error while loading shared libraries: libGLESv2.so.2: cannot open shared object file: No such file or directory

[meveric]

please give the output of ls -l /usr/lib/arm-linux-gnueabihf/libGLESv2*

[Chromoris]

Code: Select all

ls -l /usr/lib/arm-linux-gnueabihf/libGLESv2*
lrwxrwxrwx 1 root root 21 Jan 26 01:36 /usr/lib/arm-linux-gnueabihf/libGLESv2.so -> mesa-egl/libGLESv2.so

[meveric]

well looks like a lot of stuff is missing here.. it should look something like this:

Code: Select all

ls -l /usr/lib/arm-linux-gnueabihf/libGLESv2*
lrwxrwxrwx 1 root root 14 Mär 14 17:22 /usr/lib/arm-linux-gnueabihf/libGLESv2.so -> libGLESv2.so.2
lrwxrwxrwx 1 root root 16 Mär 14 17:22 /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 -> libGLESv2.so.2.0
lrwxrwxrwx 1 root root 18 Mär 14 17:22 /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0 -> libGLESv2.so.2.0.0
lrwxrwxrwx 1 root root 13 Mär 14 17:22 /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 -> ../libMali.so

where your's should probably point to mali-egl/libmali.so or something like that.

[Chromoris]

manually recreating the syslinks has fixed that problem previously, but that still leaves me with the following error:

Code: Select all

libEGL warning: DRI2: failed to open exynos (search paths /usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)

After some searching I found this forum topic: viewtopic.php?f=79&t=5078
Looking at my situation I have exactly this problem. Now I cannot uninstall libegl1-mesa due to package errors, and looking at mali-x11, I'm seeing some strange things (something isn't working right I think)

Code: Select all

ls -la /usr/lib/arm-linux-gnueabihf/mali-egl/
totaal 18228
drwxr-xr-x   2 root root     4096 Jul 27 00:20 .
drwxr-xr-x 119 root root   114688 Jul 27 00:20 ..
-rw-r--r--   1 root root       38 Jul  2  2016 ld.so.conf
lrwxrwxrwx   1 root root       11 Jul 18 23:22 libEGL.so -> libEGL.so.1
lrwxrwxrwx   1 root root        9 Jul  2  2016 libEGL.so.1 -> libEGL.so
lrwxrwxrwx   1 root root        9 Jul  2  2016 libEGL.so.1.4 -> libEGL.so
lrwxrwxrwx   1 root root       17 Jul 18 23:22 libGLESv1_CM.so -> libGLESv1_CM.so.1
lrwxrwxrwx   1 root root       15 Jul  2  2016 libGLESv1_CM.so.1 -> libGLESv1_CM.so
lrwxrwxrwx   1 root root       15 Jul  2  2016 libGLESv1_CM.so.1.1 -> libGLESv1_CM.so
lrwxrwxrwx   1 root root       14 Jul 18 23:22 libGLESv2.so -> libGLESv2.so.2
lrwxrwxrwx   1 root root       12 Jul  2  2016 libGLESv2.so.2 -> libGLESv2.so
lrwxrwxrwx   1 root root       12 Jul  2  2016 libGLESv2.so.2.0 -> libGLESv2.so
-rwxr-xr-x   1 root root 18537584 Jul 19 06:09 libmali.so
lrwxrwxrwx   1 root root       14 Jul 18 23:22 libOpenCL.so -> libOpenCL.so.1
lrwxrwxrwx   1 root root       12 Jul  2  2016 libOpenCL.so.1 -> libOpenCL.so
lrwxrwxrwx   1 root root       12 Jul  2  2016 libOpenCL.so.1.1 -> libOpenCL.so

Those syslinks don't seem right, and I've already tried to fix the situation by reinstalling mali-x11.

However, this did fix the situation for me:
- Deleted mesa-egl.
- Created the syslinks again (and this time pointing to the mali driver, and not mesa-egl, which gave me the error message on the top of this post), using:

Code: Select all

sudo ln -s /usr/lib/arm-linux-gnueabihf/mali-egl/libmali.so libGLESv2.so.2
sudo ln -s /usr/lib/arm-linux-gnueabihf/mali-egl/libmali.so libEGL.so.1

And now it works again.

I think that when upgrading the mesa egl packages, the syslinks somehow got removed. Now that the correct links have been made, things work again.
I'm still not sure as to how this could have hapened, but fixed is fixed. Still a bit curious about the symlinks above.

[meveric]

yeah these symlinks are strange:
libGLESv1_CM.so -> libGLESv1_CM.so.1
libGLESv1_CM.so.1 -> libGLESv1_CM.so
That's a loop and can't work!
Same goes for EGL, GLESv2 and OpenCL.

[gregb49]

Thanks for the useful thread.
KODI only runs for about a minute for me.
History. I received my XU4 a few days ago, updated it, and tried KODI. It wouldn't run at all. I have just updated it again; rebooted, and now KODI will run for about a minute before crashing. All I see before the crash is

17g-kodi.jpg (6.59 KiB) Viewed 3476 times

with a circle in the middle that says 100. ls -l gives:

Code: Select all

 root 48 Jul  3  2016 /usr/lib/arm-linux-gnueabihf/libGLESv2.so -> /usr/lib/arm-linux-gnueabihf/mali-egl/libmali.so

mpv Media Player will play SD videos as long as I don't try to play them full screen, and VLC just cannot cope - sound with a still picture is all I get.
Other info

Code: Select all

lsb_release -irc
Distributor ID:	Ubuntu
Release:	16.04
Codename:	xenial
uname -or
4.9.37-49 GNU/Linux

I hope that was informative.
Edited, because I notice I have a KODI crash log. It would appear that KODI tried to re-initialise many times. This is from the end of the log.

Reinitializing
17:48:44.125 T:2462556928 NOTICE: CDVDVideoCodecMFC::Open - MFC Setup succesfull (704x576, linesize 704, format 0x32314d4e), start streaming
17:48:44.132 T:2462556928 ERROR: CLinuxV4l2Sink::DequeueBuffer - Error dequeueing buffer. Device s5p-mfc-dec, Type 10, Memory 1. Buffer 0, errno 5
17:48:44.132 T:2462556928 ERROR: CDVDVideoCodecMFC::Reset - Codec Reset. Reinitializing


############### END LOG FILE ################

[odroid]

Kodi still has some issues with Kernel 4.9.
Please try Kernel 3.10 if your main application is Kodi.

[gregb49]

Thanks. Having some trouble re-flashing the eMMC, but will try 3.10

[gregb49]

I have tried flashing my eMMC card using etcher and DD through Linux and etcher through windows and also flashing two different SD cards with 3.10. My XU4 will no longer boot. I can see all the files on my PC so the cards look OK. I've also used various uSD holders as recommended but no success. The red and steady blue light come on on the XU4, but nothing further. No HDMI output. I've even disconnected everything except power supply and HDMI. I think my XU4 is now dead. Sadly, I think this brings to an end my painful foray into the world of the Odroid development boards.

[odroid]

If the blue LED is solid on with eMMC, your board must be alive.

Did you set the slide switch for SD boot mode when you tried SD cards?

If you want to keep testing the eMMC module, try this eMMC recovery process.
viewtopic.php?f=53&t=6173

[gregb49]

Thanks odroid
I think this worked, but I’ve got to take a break. I hope the following is of use to others.
Yes I had used the SD switch.
I couldn’t use xz -dk as that reported “File format not recognised” so used Engrampa GUI instead to unzip the archive.
Then used DD, in my case

Code: Select all

sudo dd if=android-4.4.4-alpha-4.9-sd2emmc_installer-odroidxu3-20170517.img of=/dev/sdd bs=1M conv=fsync
[sudo] password for mate: 
500+0 records in
500+0 records out
524288000 bytes (524 MB, 500 MiB) copied, 149.311 s, 3.5 MB/s

Then sync 5 times.

I tried three different micro SD cards with almost the same result. Steady red and steady blue LEDS, fan on constantly, but no picture. This was with only the power supply and HDMI lead attached.

With two sd cards (both 8GB Kingston), the XU4 turned off after 2minutes 9 seconds and 2 minutes 0 seconds.(ie steady red LED, no blue and no fan). I am assuming that the third, a 32GB Samsung card was not functioning correctly (It had worked previously with an RPI2).

As I was about to give up, I tried booting from the eMMC card (32GB), no HDMI output but then suddenly I had a flashing blue light, the fan stopped and Android appeared on the screen. So you were right, the XU4 is working. Now, when I feel brave enough, I’ll embark on getting back to kernel 3.10 and ubuntu. Thanks for your patience. RMA no longer required. However, I am intrigued as to why I didn’t ever see a picture from the sd card boots.

[odroid]

Try "Etcher" to reduce many flashing issues.
https://wiki.odroid.com/troubleshooting ... s#flashing

[gregb49]

Now on my 8th reflash, I've finally got Ubuntu 16:04 Kernel 3.10 running. Howere if I carry out the mandated update, upgrade, dist-upgrade, KODI will no longer work and neither will some other packages. I'm sticking with a non updated 16.04 for the time being. It works well but with some expected limitations.
Etcher will not install on my computer, for some reason.

[DarkBahamut]

There are broken updates in the package list, which leads to the issues in this thread. Doing a fresh install and a full update probably will break Kodi and other packages. We had to fix ours after the updates also.

The Mali X11 r17p0 package appeared to contain some circular references when we checked, maybe not installing that will allow you update while keeping everything working.

[fabien44]

Kodi still has some issues with Kernel 4.9.
Please try Kernel 3.10 if your main application is Kodi.

Hello,

why Kodi cannot run properly with 4.9? Is there a fix soon?

[odroid]

We've tried to find a root cause with many forum members but we couldn't find it yet.
There were a few threads we discussed.
This is an example.
viewtopic.php?f=95&t=22627&start=50&hil ... kernel+4.9
It is quite complicated and we need more time to fix it.

[Tomas J.]

After installing ubuntu from image "ubuntu-16.04-mate-odroid-xu4-20170731" Kodi (and VLC) don't work - the same problem as in first post. Will there be a fix soon?

[odroid]

20170731 version is based on Kernel 3.10.
About the VLC segfault issue, refer this link.
viewtopic.php?f=99&t=27976

[Tomas J.]

I mean error while loading shared libraries: libGLESv2.

[mdrjr]

the libEGL issue is fixed now, just released an update.
some idiot that is typing this screwed the package

Sorry guys.