Kodi reloading every half minute after burst install (openelec 6.0.3, raspberry)

[Former user]

I have just installed this evening the burst after upgrading quasar to the new available version in the repro. I am not sure what was the burst versions it installed, the thing is that after that, kodi (and not my raspberry) was being reloaded the skin every 30 seconds more or less. I guess is the skin what was being reloaded as I was connected through ssh and could still run commands.

I have not being able to find out any error message that could help me in finding the root cause, so I have decided to open here this ticket.

I am attatching you several crash logs, right after a uninstall burst kodi has stopped reloading the skin.

Versions: OpenELEC:~ # uname -a Linux OpenELEC 4.1.18 #1 SMP Mon Feb 29 20:48:22 CET 2016 armv7l GNU/Linux

[Stewart Cakemyer]

Burst doesn't do anything unless called by Quasar, so it's obviously not actively causing this. The issue here is twofold, first you're running Kodi 15 which has very spotty SSL support, so even if things kinda work, many providers probably won't be reachable anyway. Second, you still have the Pulsar repository installed, and Quasar is catching its calls for repo updates (which it probably shouldn't anyway, will look into that), but either way you should remove that old Pulsar repository. Bottom line is that this is not about Burst, worst case it's something in Quasar, but basically you should just clean up and upgrade your setup.

Thanks for the report and logs. Although I'm closing this as invalid, I do appreciate seeing how Quasar holds up on old and crusty versions of Kodi ;) Since Kodi 17 is close to being released, even support on a best-effort basis for Kodi 15 will be dropped, so you might as well upgrade sooner than later.

Cheers

[Stewart Cakemyer]

Not a Burst issue

[Raúl Cano]

Hi Anonymous, I just came in to say that I have had the same issue (Openelec 6.0.3, Raspberri Pi 3). Following @scakemyer advice, I have updated my setup to Openelec 7 and the issue dissapered.

Also, I want to thank you @scakemyer for all the good work you are putting here. Cheers!