Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
Sounds like file system corruption, specifically the guisettings.xml file (probably).
How are you shutting down the Pi? Are you selecting "Power off" from the Kodi menu, or are you turning off the power supply at the wall/pulling the power cable while the Pi is still running Kodi?
Also worth a try is a different (more powerful) PSU and different USB cable - make sure it's not too thin as cheap cables can result in too much voltage drop.
If you ever see a rainbow-coloured square in the top right of the display (or the red power LED turns off) then your PSU is not supplying enough voltage.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Posts: 320
Joined: Aug 2012
Reputation:
3
What memory card are you using?
Make sure its at least a class 6 or class 10 ideally.
I would think that it may be a error on your memory card if you have a spare make a complete copy of your card and write it onto a new card and see if it works on there.
Posts: 320
Joined: Aug 2012
Reputation:
3
Its possible that a update is causing it.
Make sure OSMC automatic updates are turned off most addons have a option to turn off automatic updates also.
Once all the automatic updates are turned off on everything do a few reboots and see if anything happens and if it seems to be working OK you could then turn on automatic updates on one at a time and see which one causes it to mess up.
Would be best turning on Kodi debug log and reading what happens on startup.
Posts: 15
Joined: Aug 2015
Reputation:
0
Thank you, I didn't see this thread (probably because I used "Kodi" as keyword and not OSMC).
Vviljanen and Kilobyte seems to have exactly the same issue. I'll try that way.
Posts: 15
Joined: Aug 2015
Reputation:
0
I didn't see the issue for a few days, so I cross my fingers and wait for this release.
(Excuse the newbie : will Kodi automatically install this fix when it will be released?)
Posts: 15
Joined: Aug 2015
Reputation:
0
It did again - fortunately, I saved my guisettings.xml.
I restored it and got my skin and settings back... but this problem is quite annoying...
Posts: 3
Joined: Jan 2017
Reputation:
0
any solution to this issue yet? This happens to me over and over. Normally when I log out of one profile and into the next.
Posts: 15
Joined: Aug 2015
Reputation:
0
I can't help you, it stopped just like it started and it never happened again.
Posts: 1,600
Joined: Dec 2009
Reputation:
124
This is an old post, so I don't believe OSMC is affected anymore.
There are scenarios in CApplication where guisettings is written out multiple times. This increases the chance of corruption, especially if you have a systemd unit which will kill processes after a certain time if you call a reboot or shutdown. Kodi does not have a native sigterm handler.
We used to have a patch to prevent write out if the contents of guisettings.xml would be unchanged
This doesn't seem to be an issue anymore in OSMC after reworking our sigterm handler.
Assuming you are using systemd, make sure you are giving Kodi 30s before SIGKILL. There are some versions of systemd where this is not honoured and this is a regression.