Kodi Sad Face Loop

Help and Support
1

Hi,

I installed OSMC on an RPI2 a couple of days ago, had it working fine with a hub and 2 USB HDDs, 1 for music, 1 for movies. Seemed to be working fine.

I installed the Samba server and shared a music directory on one of the HDDs for other RPIs around the house running Volumio.

I then installed transmission daemon and got that working, but was done entirely through ssh, wasn’t watching the screen Kodi outputs to.

I’ve now turned on the tv to see Kodi is showing its sad face for 10 seconds, then a blank screen, then sad facing again.

Here’s my kodi log with the log level set to debug from reading a few other threads.

kodi.log

What other logs etc do I need to look at to find why its not happy? Or what should I try?

2

Transmission should be installed from the MyOSMC app store. Remove your SSH installed instance and install as provided.

3

I’ve already tried apt-get removing it, then rebooting, and it still just sad face loops.

4

Your kodi.log doesn’t show anything of use, please post your system journal:

sudo journalctl | paste-log
5

http://paste.osmc.io/ijihazekis

Sep 22 20:18:02 osmc mediacenter[255]: Kodi exited with return code 139 after 0 hours, 0 minutes and 1 seconds

Seg fault?

Thanks for your help.

6

Yes exit code 139 indicates a segfault. I was hoping to see another error in the journal but there’s nothing - it’s just crashing instantly.

Is it a MySQL install ?

I would check that the root file system is not read only and not out of space. Can you provide the output of the following ?

mount | paste-log
df -h | paste-log

If the root partition is rw and there is at least 300MB free then the next thing I would suggest would be to rename your .kodi folder to see if it is something corrupt there that is causing the crash.

7

Mount: http://paste.osmc.io/lojatizedi
df: http://paste.osmc.io/naqihewuba

So that all looks fine to me. Renamed .koid to .bkup_kodi, restarted, and now getting an exit code of 134, and something about free being called on an invalid pointer.

Journalctl: http://paste.osmc.io/xuzidipefi

Unless there’s something obvious, I think I’ll go a re-install. I think from memory I picked the latest version during the installer, should I choose a previous one?

8

One last thing you could try is to reinstall the Kodi package:

sudo apt-get install rbp2-mediacenter-osmc --reinstall

If that works then some of the Kodi files have got corrupted somehow.

9

Just noticed a very strange error in your new log:

Sep 22 20:50:32 osmc mediacenter[252]: *** Error in `/usr/lib/kodi/kodi.bin': free(): invalid pointer: 0x0318e3cc ***
Sep 22 20:50:32 osmc mediacenter[252]: Can't open device file: /dev/vcio (-1)
Sep 22 20:50:32 osmc mediacenter[252]: Try creating a device file with: sudo mknod /dev/vcio c 100 0
Sep 22 20:50:32 osmc mediacenter[252]: * failed to open vchiq instance
Sep 22 20:50:32 osmc sudo[304]: pam_unix(sudo:session): session closed for user osmc
Sep 22 20:50:32 osmc mediacenter[252]: Kodi exited with return code 134 after 0 hours, 0 minutes and 8 seconds

This will be why Kodi is failing to load, however I don’t know what has caused this - have you installed a different kernel by any chance, for example by running rpi-update ?

Did you have any failed updates ? If so can you post the apt term.log:

paste-log /var/log/apt/term.log
10

http://paste.osmc.io/mevisiseje

Now that you mention it, I did run apt-get update / upgrade I think, while playing around with an NFS share.

Re-installing Kodi now… or should I just start over and not do an update?

I liked that with RaspBMC I was able to install other apps / my own python apps alongside without seeming to break XMBC, is that a definite no-no for OSMC / Kodi?

11

Have re-imaged the SD card, and then installed samba, transmission and tvheadend from the OSMC app store and is all working now, going to assume it was something in the apt-get update/ upgrade that killed it.

12

That would be a flawed assumption. There’s no reason that should be causing an issue, dozens of other users do it without problems. Though if you are trying to update/upgrade by command line, OSMC recommends update && dist-upgrade as opposed to a simple upgrade.