Skin sort of frozen?

My OSMC running on a Raspberry Pi 2 has ceased to work properly. It starts but fails to load its skin completely. Recently added moives, skin short cuts, those sort of things just doesn’t show.

I removed guisetting.xml to change skin from Unity to the default, but the problem persists.

My TV remote can no longer control Kodi. I can however access it via other means. SSH, FTP and the web interface all work. So does Yatze, my Android Kodi remote of choice.

I can start media via Yatzes interface (not navigating Kodi). It plays.

But when I try to use Yatze as a remote, the first press of a direction shuts down the GUI and I get the OSMC sad-face-something-went-wrong screen. Then I’m returned to the start menu, again not showing properly.

I have noticed something which might help explain what happend, but I need help understanding it. During the last few days, I was getting »Skin short-cut error« or something every time I returned to the home menu. There was nothing wrong with any of my shortcuts, so I put the issue of my mental list of things to investigate later. The error message said something about looking at an error log for details.

Today I tried to start first one then another streaming app. Both failed, and gave an error message doing so (I think it was just [app name] failed to start).

That’s when I restarted OSMC for the first time in 3 days (checked System Info before hand)). And it made everything worse … :wink:

I checked /temp/kodi.log for some clue as to what’s happening, but cant really find anything obvious.

These are the warings and errors contained:

17:05:32 44.218739 T:1958269488 ERROR: DBus: Error org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
17:05:36 47.668743 T:1958269488 WARNING: JSONRPC: Could not parse type “PVR.Details.Channel”
17:05:36 47.669743 T:1958269488 WARNING: JSONRPC: Could not parse type “PVR.Details.ChannelGroup.Extended”
17:05:36 47.710297 T:1958269488 WARNING: JSONRPC: Could not parse type “GUI.Property.Value”
17:05:36 47.727428 T:1958269488 WARNING: JSONRPC: Could not parse type “Setting.Details.SettingList”

Please provide complete logs. The errors you have listed are of no consequence and present in nearly all installs.

Enable debug logging and either upload all logs by use of the MyOSMC addon log uploader or the resulting URL when issuing grab-logs -A from a terminal session.

Not being able to access the MyOSMC addon I used SSH:

osmc@osmc:~$ grab-logs -A Traceback (most recent call last): File "/usr/lib/python2.7/", line 563, in <module> main() File "/usr/lib/python2.7/", line 545, in main known_paths = addusersitepackages(known_paths) File "/usr/lib/python2.7/", line 272, in addusersitepackages user_site = getusersitepackages() File "/usr/lib/python2.7/", line 247, in getusersitepackages user_base = getuserbase() # this will also set USER_BASE File "/usr/lib/python2.7/", line 237, in getuserbase USER_BASE = get_config_var('userbase') File "/usr/lib/python2.7/", line 582, in get_config_var return get_config_vars().get(name) File "/usr/lib/python2.7/", line 509, in get_config_vars import re ValueError: bad marshal data (unknown type code)

I’m not sure how this should look but that doesn’t contain a URL as far as I can tell …

I read a little about log files and figured maybe I needed to turn on debugging.

So I followed this and created advancedsettings.xml in home/.kodi/userdata

In this file, I copied over the code from 1.2.2 advancedsettings.xml for input devices, then rebooted and ran grab-logs -A.

Didn’t make a difference.

You have a problem with file corruption; thats at least the problem that python had with grablogs.

It might be that your SD card is dying.

If that is the case, I strongly recommend grabbing all your userdata off the SDcard while you still can.

How can I know it’s a problem with the microSD card?

And grabbing the userdata, is that just copying over everything in /home/-kodi/userdata to a new medium?


Try a fresh install on a different SD card?