Skip to content
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

Super Favourites error on startup #42

Open
mattmartinolc opened this issue Aug 9, 2016 · 4 comments
Open

Super Favourites error on startup #42

mattmartinolc opened this issue Aug 9, 2016 · 4 comments

Comments

@mattmartinolc
Copy link

Not sure what is going on. When I start kodi on any of two windows machines, and one android machine all running kodi 16.1 Jarvis there is a message just after startup "Super Favourites error. Check log for more information". Yet the superfavourites lists all work and everything seems fine. Nothing I can find in the log either.

@mattmartinolc
Copy link
Author

nevermind I got it to log finally .. my advancedsettings.xml was set to stop logging

01:47:20 T:4108 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<-- - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS! Error Type: <type 'exceptions.ImportError'> Error Contents: Failed to import time because the import lockis held by another thread. Traceback (most recent call last): File "C:\Users\Beth\AppData\Roaming\Kodi\addons\plugin.program.super.favourites\service.py", line 31, in <module> utils.verifyRunning() File "C:\Users\Beth\AppData\Roaming\Kodi\addons\plugin.program.super.favourites\utils.py", line 250, in verifyRunning day = datetime.datetime.today().day ImportError: Failed to import time because the import lockis held by another thread. -->End of Python script error report<--

@spoyser
Copy link
Owner

spoyser commented Aug 9, 2016

Thanks for that, caused due to a bug in Python itself, will add a work around and push ASAP.
It shouldn't cause too much of an issue (switching context menu on or off might not work, but everything else should be okay)

@spoyser
Copy link
Owner

spoyser commented Aug 9, 2016

Can you check 1.0.55 to see if problem resolved, hard for me to test as it doesn't error on my mahine

@mattmartinolc
Copy link
Author

Problem seems to be solved now on all the affected machines (not all were affected). Keep up the good work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants