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

Quasar doesn't start on latest OSMC release (based on Kodi 17) #714

Closed
ghost opened this issue Feb 9, 2017 · 8 comments
Closed

Quasar doesn't start on latest OSMC release (based on Kodi 17) #714

ghost opened this issue Feb 9, 2017 · 8 comments

Comments

@ghost
Copy link

ghost commented Feb 9, 2017

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:

  1. Run previous OSMC release on Raspberry pi 3
  2. Upgrade OSMC using apt or from the GUI
  3. Remove old Quasar version 0.9.66 and install 0.9.68
  4. Start quasar from gui (which fails on my setup)

My environment details:

  • Version used: 0.9.68
  • Environment name and version: OSMC (latest), Kodi 17

Any help would be greatly appreciated, thanks.

@scakemyer
Copy link
Owner

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.

@ghost
Copy link
Author

ghost commented Feb 9, 2017

Here's a complete log: http://paste.ubuntu.com/23962961/

Steps taken:

  1. Removed Quasar
  2. Enabled debug logging
  3. Installed Quasar
  4. Stopped and pasted debug logging

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.

@scakemyer
Copy link
Owner

Start by nuking /home/osmc/.kodi/userdata/addon_data/plugin.video.quasar, it makes no sense that it thinks bin/linux_armv7/quasar is a directory...

@scakemyer
Copy link
Owner

Restart your box after doing that, seems you had a process already running too

@ghost
Copy link
Author

ghost commented Feb 9, 2017

Removing the directory worked. Thank you very much!

@ghost ghost closed this as completed Feb 9, 2017
@scakemyer
Copy link
Owner

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.

@vvinni
Copy link

vvinni commented Feb 4, 2018

I have the same problem and removing /home/osmc/.kodi/userdata/addon_data/plugin.video.quasar
Do not worked...

I don't know how to get my log... Anyone could help?

@vvinni
Copy link

vvinni commented Feb 4, 2018

Founded the way...

https://paste.osmc.tv/debumogavu

My log

This issue was closed.
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