Kodi won't start after October update

Help and Support
#1

After manually kicking off the October update everything seemed to work as normal, but on the restart I just get a black screen. I have tried rebooting and manually upgrading via SSH but no job.

Nothing is being logged to .kodi/temp/kodi.log and checking the service status shows;

osmc@living:~$ sudo systemctl status mediacenter
* mediacenter.service - media center application
   Loaded: loaded (/lib/systemd/system/mediacenter.service; enabled)
   Active: active (running) since Mon 2016-10-31 21:32:39 NZDT; 2min 17s ago
 Main PID: 458 (mediacenter)
   CGroup: /system.slice/mediacenter.service
           `-458 /bin/bash /usr/bin/mediacenter

Oct 31 21:34:56 living mediacenter[458]: libpng warning: Ignoring bad adaptive filter type
Oct 31 21:34:56 living mediacenter[458]: libpng warning: Ignoring bad adaptive filter type
Oct 31 21:34:56 living mediacenter[458]: libpng warning: Ignoring bad adaptive filter type
Oct 31 21:34:56 living mediacenter[458]: libpng warning: Ignoring bad adaptive filter type
Oct 31 21:34:56 living mediacenter[458]: libpng warning: Ignoring bad adaptive filter type
Oct 31 21:34:56 living mediacenter[458]: libpng warning: Ignoring bad adaptive filter type
Oct 31 21:34:56 living mediacenter[458]: libpng warning: Extra compressed data.
Oct 31 21:34:56 living mediacenter[458]: libpng warning: Extra compression data.
Oct 31 21:34:56 living mediacenter[458]: libpng error: IDAT: CRC error
Oct 31 21:34:56 living mediacenter[458]: could not load image: Success

What else can I check to see what is going wrong here?

Thanks,
Ben

#2

Suggest to upload full logs grab-logs -A to get a better picture of what might be wrong.

#3

Thanks @fzinken - http://paste.osmc.io/ubofejazaf

#4

Seems to be a corrupted system

Oct 31 21:32:39 living mediacenter[458]: /usr/lib/kodi/kodi.bin: error while loading shared libraries: libbrcmGLESv2.so: cannot open shared object file: No such file or directory

Maybe try manually to update with

sudo apt-get update
sudo apt-get dist-upgrade

And check the output, if that doesn’t work maybe a reinstall would be the fastest way (but check SD Card and Powersupply before).

#5

I have already tried the manual upgrade, it is reporting nothing to do.

This was a new install a few weeks ago (after a corruption then). It is running off a 2A iPad charger (RPi3).

I will try reinstalling on a new SD card I have here.

Thanks for having a look. Frustrating this keeps happening after years of trouble-free operation!

I thought the RPi3 was supposed to be much better with SD card corruption issues?

#6

Not recommended, the RPi3 is specified with 5V/2.5A and best not to use any “charger”.
If you get into corruption with updates it either is a power supply or SD Card problem. Suggest to only use high quality SD Card cards from a trusted resources.

#7

I admit I didn’t know that - I thought a 2A supply was plenty. I will order a proper supply now from ModMyPi!

#8

How about ordering it from OSMC story to support OSMC :slight_smile:

But to be honest a bad SD Card might be another likely culprit. There is bad shit of SD Cards out there.

#9

Ah of course - I didn’t realise they stocked them - I will definitely order from there. I just bought two of the OSMC remotes and they arrived nice and quick and are fantastic, so more than happy to support the store. Thanks again!

#10

Your system is definitely corrupted. I could suggest a couple of commands, but to be honest it looks like more than one or two problematic packages, so it may be best to start over.

I think reinstalling OSMC once every 18 months is realistic. There are some backup options in My OSMC which may help you

Thanks for supporting OSMC :smile:

Sam

#11

Appreciate the feedback guys - I have rebuilt using a new SD card and everything is looking good again. Really do love this system!

1 Like
#12

I have a similar problem after the update. I’m stuck in the smiley face down loop.

I think some configuration breaks the system after the update. Here is the output from grab-all http://paste.osmc.io/atebulocix

I’ve moved the .kodi folder away and started kodi and it comes up.

osmc@osmc:~$ kodi-standalone 
unknown
unknown
mv: failed to preserve ownership for ‘/boot/config.txt’: Operation not permitted
Segmentation fault
Crash report available at /home/osmc/kodi_crashlog-20161031_230027.log
unknown
unknown
mv: failed to preserve ownership for ‘/boot/config.txt’: Operation not permitted

Any ideas how I can fix my config or should I not bother and just re-enter all the settings?

Update: here the output from the crashlog mentioned above http://paste.osmc.io/aboterijah

Update 2: it’s not impossible I’m a victim of the bigger Power supply needs as I have two USB discs attached (but also have an icybox 3.5A PSU)

#13

You shouldn’t launch Kodi with the kodi-standalone command.

#14

Ok and thanks for the super quick response. Have I broken it substantially?

#15

I haven’t checked your log to see what other commands you have run. The update is generally well received, so a reinstall is probably a good idea if you’ve been playing with it.

#16

@PeterHandke your log file has many errors such as these

23:00:24 2646.491943 T:1757410288 ERROR: CCurlFile::Open failed with code 404 for http://download.osmc.tv/kodi/addons/jarvis/metadata.themoviedb.org/metadata.themoviedb.org-3.9.2.zip.md5

You appear to have a network/internet connection problem.

Given that your full logs reveal that external connections are being routed through TOR I would disable that first and try again.