Outside of the onetime error all seems to function normally. Also I see no way to reproduce the failure, so I can’t help with debug logs or is debug logging already activated by default?
That’s to be expected – it’s a bug with script.skinshortcuts that needs fixing eventually.
If it’s anything that needs fixing within Skin Shortcuts itself Sam, let me know - I’m the maintainer of that script.
So it seems the error its down to the Epg11.db that seems to be the only file i had to delete in order to get the new builds going. I suspect that is because the skin is trying to read the EPG and i don’t have a backend enabled
Sorry, is was trying to fast. I eventually just renamed the addons folder, let it create a new one and copied only the addons i actually use. I can see from top that kodi.bin keeps running now. Once i get home i’ll find out how much I wrecked it 
Cant believe that no debug logs was posted at all.
Think that should be a given if you got issues with a nightly build.
That’s handy – I’ll send you a PM.
Also had the issue with Kodi restarting repeatedly. No indications in log that I could find, and Kodi always stopped logging right after repositories and just as binary add-ons were being loaded with no errors/warnings.
Tried as Lawrence_Curtis mentioned to help confirm/narrow scope and it did not work. I did notice that Addons26.db-journal existed at every ‘sad face’ until restart in my case so I removed that database and then with the single ‘sad face’ restart it started successfully.
After re-enabling add-ons in small batches. I hit 2 that required updates (not for Krypton compat.), hitting update all sent it back into the restarting loop with ‘waiting on add-ons to update’ message in the log. (still no errors/warnings)
Starting over, I enabled those add-ons individually and manually updated them and everything seems stable again.
Been a while since I’ve had to manually update an individual add-on so it may be normal, but it showed the same version twice with only 1 repo to install from. (only mentioning as it ties to updating may/may not be related)
Apologize for no logs. Got caught in the process and didn’t save any throughout.
Enable Debugging and comeback when you do have a log to produce.
Hi!
In the test build of Kodi 17 the “Picture Slideshow Screensaver” no longer works. When the screensaver activates, I see an animation of grey circles circling, no picture slideshow is displayed.
The screensaver worked fine in the “August Update” of OSMC (Kodi 16).
I then updated to this testing version including the mediacenter package version “16.8-160, 15 Sep 2016”, exhibiting the bug as described above. Logs: http://paste.osmc.io/melesipulu
Installing the “September Update” of OSMC did not change the symptoms.
Updating the mediacenter to version “16.8-162, 05 Oct 2016” did not change the symptoms. Logs: http://paste.osmc.io/gogarutare
I appreciate any suggestions.
Cheers
Kosh
Telling us what the errors are will certainly help!
Not sure what the problem may be. I advise waiting a few more builds and reporting back if it persists; Kodi test builds are still quite experimental.
Cheers
Sam
Indeed, I shall do that.
I just found that the problem disappears in a new profile (i.e. after I delete ~/.kodi and redownload and reconfigure the screensaver, although it is the same add-on version).
I’m having the infinite boot loop error as well. Here is the output of grab-logs -A
http://paste.osmc.io/wahepopoha
I went back to 160 turned on debug logging and did the upgrade again, here are those logs:
http://paste.osmc.io/eqetinijuq
Thanks
So what error are you getting? Does the update go through?
Can you enable debug logs for the infinite boot loop.
16.8-162, 05 Oct 2016: Based off OSMC commit (c527e25a2) and newclock5 (61bcde17)
XBMC:
[cmake] Fix always outdated targets (PR:10614, 2 commits, 2 files changed)
[doxygen] add support to show function with version change text (PR:10621, 1 commit, 3 files changed)
Create italian.xml (#10545) (dd13b734)
OSMC:
Disable unwanted notifications rom 3rd parties (c527e25a2)
I added this to my first post a few minutes after I posted it.
Hey,
I started testing the build a few days ago and it is mostly looking good.
One problem I found is that the UPNP Server I am running through Kodi no longer displays the hostname of my raspberry but instead shows up as unnamed device.
In Kodi 16 I used to be able to configure the device name in the GUI this is no longer possible in Krypton (Services → General was the old location)
Looking at the log I found the error msg
11:02:09 566.663940 T:1959108608 NOTICE: load settings…
11:02:09 566.704285 T:1959108608 ERROR: CSettingString: error reading the default value of “services.devicename”
11:02:09 566.704407 T:1959108608 WARNING: CSettingGroup: unable to read setting “services.devicename”
Since it is no longer available in the GUI the setting for the devicename gets purged from the guisettings.xml (at least that’s my understanding).
So I added
<advancedsettings>
<loglevel>2</loglevel>
<services>
<devicename default="true">Kodi</devicename>
</services>
</advancedsettings>
to the advancedsettings.xml but judging from the log it seems that file only gets parsed after the error happens. It also seems that full debug mode only gets enabled after the error happens.
But I am not that familiar yet with how Kodi works so this could also be completely wrong. Would be great if somebody could help me figure out what the problem is.
I am also attaching the full log in case that helps.