After playing with Alpha 4 for couple of hours I cannot open OSMC setting program anymore. It says Script fails on screen and this is what I get in log
14:56:19 T:2774529056 NOTICE: Thread LanguageInvoker start, auto delete: false
14:56:19 T:2774529056 NOTICE: -->Python Interpreter Initialized<–
14:56:19 T:2774529056 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<–
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <class ‘socket.error’>
Error Contents: (11, ‘Resource temporarily unavailable’)
Traceback (most recent call last):
File “/usr/share/kodi/addons/service.osmc.settings/default.py”, line 11, in
sock.connect(address)
File “/usr/lib/python2.7/socket.py”, line 224, in meth
return getattr(self._sock,name)(*args)
error: (11, ‘Resource temporarily unavailable’)
–>End of Python script error report<–
16:36:11 T:2799694880 NOTICE: Thread JobWorker start, auto delete: true
It worked before, it even downloaded some updates.
We have identified and fixed some bugs in the OSMC settings update that is probably the cause of the errors you’re reporting. To fix this please run a full check for updates.
Depending on which version of the addon you currently have you might find the update function isn’t working so to manually install the latest updates run the following at the local console or via ssh:
Yes, that helped, I can open settings dialog again.
Just one minor bug introduced with this - in updates panel, last tab (manual controls) has three fields - scan now, install now and “grep osmc” . I assume the last one is not supposed to be there…
Correction - I was able to access it once. I browsed through tabs, I noticed some were corrected. I did not change anything, I clicked on search for updates. Later I wanted to go to settings again, it did not open again. Here is current log
Mine is 1.66.
In /var/tmp I see these
-rw-r–r-- 1 root root 253394 Feb 5 13:53 OSMC_python_apt_log.txt
srwxr-xr-x 1 osmc osmc 0 Jan 1 1970 osmc.settings.sockfile
srwxr-xr-x 1 osmc osmc 0 Jan 1 1970 osmc.settings.update.sockfile
I can do it only via ssh as I have no keyboard there. How do I stop kodi properly so that I cam remove those two files ?
Mine is versio 1.66, too. I removed the files like you said (successfully, I checked the directory afterwards, it was empty). Then rebootet. Still no luck with OSMC settings.
In my case I found that it “broke” after I restored my userdata using
Thanks for the hint - I just backed up the .kodi folder from my Raspbmc install on another Pi and restored it to osmc and I now see the same problem as you - the settings addon won’t launch and I get the same error in the log.
My backup comes from an earlier stage of OSMC alpha 4.
Maybe another hint: I’m using a HiFiBerry DAC (RPi B). At the moment it doesn’t work either. Since it’s activated via the settings app, maybe its failure is somehow related.
As in other cases i’m using 1.66 version, deletition of socket didnt helped. I wasn’t using any kind of backup. It was a clear install with RPi2. I have installed conluence skin ( as default) and osmc skin. But osmc setting are not working in neither of skins. It’s exactly as thansen_dk said. Working right after the reebot ( if it’s launched as a first plugin) later on it’s impossible to launch it.