-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spotimc keeps asking me to restart xbmc #1
Comments
It happens on both alpha3 and alpha4 |
And here's the logs: http://pastebin.com/ttjeJw9D |
That's a strange bug. A couple of questions:
I was unable get any clue from your logs. The code involved in that issue does't seem to post useful debug info. I'll take a closer look and try to reproduce it. Thank you for the report! |
Thanks for replying so quick.
|
I have the same problem as asgerhallas. Installed Spotimc on 10.1 and then upgraded to 11.0, stuck with the restart message. Any clues? |
Hi Dedas, It's probably because the Confluence skin got copied to your userdata folder (by Spotimc running on XBMC 10.1), and now that XBMC was upgraded (comes with a new version of the confluence skin) it will pick the newer version (which is on the XBMC's bin folder). This is what is causing Spotimc to enter in an endless you-need-to-restart loop (Spotimc's fault, it should check for this). Deleting the old confluence skin on the userdata folder will do the trick. A fix for this issue will be included on the next alpha. |
Thank you! That solved it! :D |
I could not find any skin files in my userdata folder, so I ended up removing all xbmc data from the library and reinstalled Eden. That worked. And this plugin was worth the hazzle! Very well designed and usable :) |
Closing this issue. A fix was committed to the skinutils repo. |
Everytime a start the addon I get a popup saying I need to restart. I have restarted several times, restarted the computer, and reinstalled the plugin to no avail.
I can mail you the logs if you like, I don't know which parts are the interesting ones.
The text was updated successfully, but these errors were encountered: