I had major issues with bone-stock December update, which after much mucking around was related to that new SSD driver, and was addressed with dtoverlay=mmc to /boot/config.txt which appeared to work for subsequent weeks (of little use). (PI1 December Update Woes)
However after seeing a new update in January and letting it run the same behaviour is back again, ie ‘OSMC Setting Service Failed To Launch’ and My OSMC missing all its icons etc, + general errors on boot.
Your latest APT entry is End-Date: 2016-01-24 16:27:08 which was before the January update. So if you updated on 24th it would mean you just updated some minor corrections that came out after december release.
Overall I have the fear that your SD card is corrupted as there seems to be files damaged on the osmc addons.
you may want to try an upgrade from the command line but depedning on the SD card I am not sure how successful you will be sudo apt-get update && sudo apt-get dist-upgrade
If all goes thru reboot.
Good question - whatever the update on 2016-01-24 16:27:08 was what borked things… I can go through the whole process of reinstalling and reconfiguring everything, but that’s less fun when the issue isn’t diagnosed yet.
I can not see any other “issue” than a corrupted SD card which either is a result of it getting corrupted by the sdhost driver in december or just a bogus card.
So if you want to do yourself a favour I would recommend to get a new card and do a plain installation on that.
The “update” you did install consisted of a solitary bug fix update to the My OSMC addon, and the rest of the update you received was all Debian related updates not specific to OSMC, as there was a Debian point release released not long ago.
I do see one thing of interest in your log other than the error Karnage already pointed out:
depmod: ERROR: failed to load symbols from /lib/modules/4.3.3-3-osmc/kernel/drivers/media/usb/dvb-usb/dvb-usb-pctv452e.ko: Exec format error
This is an unusual error but suggests file system corruption has occurred at some point on your system. Possibly as a result of the period of time you were running the sdhost driver in early December, but it’s hard to know.
So since you are not actually running the January update, try updating again and let us know what happens. Because of that element tree error you may not be able to do so via My OSMC, so instead try:
sudo apt-get update
sudo apt-get -f dist-upgrade
Report any errors here.
We’re sorry that the software that you got for free written by people working in their spare time doesn’t quite live up to your expectations and doesn’t work perfectly for every one of the 600,000+ users using it…
And yes, I too have (and still do) contribute to OS projects and appreciate your efforts on OSMC - my annoyance wasn’t directed at you or anyone at all really, it was merely a reflection on the surprising instability I’m experiencing after a significant period of time with rock-solid use - with no strong clues yet.
If I could figure out the solution it wouldn’t be anywhere near as annoying.
The update seemed to go through OK according to the log, but the element tree issue remains. @Karnage can probably correct me but I suspect that module is bundled in the built in python interpreter in Kodi, which would mean that Kodi has somehow got corrupted during the most recent update that included a Kodi update.
You could try the following to do a forced reinstall of Kodi: (Pi 1 only below)
(The screen will go black) Then reboot from the command line when finished.
If that fixes the My OSMC error that would confirm that the Kodi install got corrupted, but if so it leaves open the question of why and how that happened - in theory it shouldn’t be possible because dpkg does checksums on files as it extracts them.