Mediacenter crash after update

thanks i followed the instruction

@ratelutz did you solved the problem with the instructions above?
I’m asking cause I have the same issue since last update and I removed all skins except osmc and confluence.

Did you activated one of the two?
Add entry in guisettings.xml <skin>skin.confluence</skin> or <skin default="true">skin.osmc</skin>

I just have skin.osmc…
do I need to add skin.confluence as well ?

No, as I wrote “or” so just one of that lines is good enough.
So you have that line in guisettings and still have a crash?
Provide full logs with grab-logs -A

no issue still exists. but i found it is not cec related because i disabled the cec adapter and medicenter is still restarting

crashed again this time with cec adapter completely disabled

logs: http://paste.osmc.io/ugecatiquq

Can you back down the overclocking?

shure but actually i am running Dez. version on to a different sdcard. i will try it tomorow and report back

We need to only concentrate on troubleshooting ONE INSTALLATION at a time… And it should be the most current update please.

i understand but it was my last resort because osmc was nearly unusable and i wanted to listen to my music right now.

tomorow i will switch the sdcard again and continue debugging the issue

disabled overclocking but still crashes
http://paste.osmc.io/gufoxemefi

Try to disable Addons. Would start with Library Auto Update.

BTW, I deleted (CEC related) from the title as that seems to be not anymore the main culprit.

disabled nearly all add-ons. nothing changed
http://paste.osmc.io/ujupekabos

try to rename .kodi and start from scrach, that fix it for me and bring some boost the performance of my pi.
stop mediacenter service then rename /home/osmc/.kodi
then start it again.
you can always revert back…

ok i will try it

That fixed it. I had to setup my add-ons and settings from scratch but no big deal.

it would be nice to get the main reason for that issue.

thanks everybody for yout help

I wouldn’t call it a solution, but more a workaround…
Anyhow I had last time when kodi version got updated similar issues and solve it in the same way.
Totally agreed with you, we should find the root cause for this one, but as can be any add-on, skin out there it is rather difficult…
It’s like with any big operating system update, yes can work, but to be sure you have the best experience, better is to start from scratch…

seems that there are other with the same / similar issue