plugin.video.quasar icon indicating copy to clipboard operation
plugin.video.quasar copied to clipboard

quasar 0.9.78 kodi 17.6 libreelec 8.2.3 crashing after running fine for month (update from 0.9.78 to 0.9.78)

Open nannyy opened this issue 7 years ago • 5 comments

Expected Behavior

quasar with quasar burst running and having a simple way to watch almost every possible movies and TV shows.

Current Behavior

Quasar crashing 3 times at startup and then saying "looks like quasar is still starting up, give it a few seconds"

Possible Solution

???

Steps to Reproduce (for bugs)

1.Start the wetek.core box.

Context

Experienced some crashes more and more often but was running till I pressed on "update" in the add-on. I'm pretty sure I was already running 0.9.78 as it is what I found in my zip files. I was on kodi 17.6 and libreelec 8.2.2. From then I wasn't able to have it work again even after several uninstalls and fresh installs even tried to fresh download the zip file. Went through issue #981 but wasn't able to find a line with armv7l on it and I'm pretty sure my machine announces herself as armv7l. tried anyway to force return to armv7 which didn't work for me. The logs I give you is after a fresh install from zip file downloaded on quasar official.

Your Environment

hw: WETEK.CORE

  • Version used: quasar 0.9.78
  • Environment name and version: 17 [Krypton] kodi 17.6
  • Operating System and version: LibreELEC 8.2.2 and 8.2.3
  • Link to Kodi debug log: http://ix.io/SfW

nannyy avatar Mar 04 '18 08:03 nannyy

hmm try to remove the addon and userdate qwasar en reinstall it

tomtomclub avatar Mar 08 '18 17:03 tomtomclub

hum yeah, forgot to mention I also removed manually all quasar related folders. where would I find the usrdate?

nannyy avatar Mar 10 '18 16:03 nannyy

kodi browser file manager in menu you see it kodi/ addon/ userdate

tomtomclub avatar Mar 12 '18 18:03 tomtomclub

https://www.youtube.com/watch?v=-XtubitjT9M

tomtomclub avatar Mar 12 '18 18:03 tomtomclub

I sometimes find this problem in windows, probably after a kodi crash, and it's caused by the presence of the lock file on the plugin folder.

luispabon avatar May 10 '18 16:05 luispabon