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
Quasar doesn't start on latest OSMC release (based on Kodi 17) #714
Comments
Ok that log isn't helping at all, sorry. I've had 0 issues with a test box I have with OSMC; it actually took more time to backup the .kodi folder than to upgrade OSMC... and everything worked perfectly afterwards. Please share the whole log of when you're trying to install Quasar and I'll look into it. |
Here's a complete log: http://paste.ubuntu.com/23962961/ Steps taken:
Just to be clear on this. If you think this has nothing to do with the Quasar code, I'll just nuke the install and see what happens next, no need to waste time on what could be a broken OSMC install from upgrading. |
Start by nuking |
Restart your box after doing that, seems you had a process already running too |
Removing the directory worked. Thank you very much! |
I'm not sure what happened there, but basically you don't have to remove Quasar before updating Kodi or Quasar itself, so it looks like just removing it didn't stop the daemon, which caused the issue when trying to reinstall it after your OSMC upgrade. |
I have the same problem and removing /home/osmc/.kodi/userdata/addon_data/plugin.video.quasar I don't know how to get my log... Anyone could help? |
Founded the way... https://paste.osmc.tv/debumogavu My log |
Hello,
Two days ago I upgraded to the latest OSMC release which is based on Kodi 17. When I reinstalled Quasar it fails to start with error message "ioerror(21 'is a directory')".
I've enabled debug logs and pasted only the relevant section when quasar logs something. The logs can be found here: http://paste.ubuntu.com/23962502/
How to reproduce:
My environment details:
Any help would be greatly appreciated, thanks.
The text was updated successfully, but these errors were encountered: