plugin.video.quasar
plugin.video.quasar copied to clipboard
scakemyer
[ERROR] Quasar malfunction on Windows Store Kodi
I've installed the Windows Store version of Kodi and it works ok for the most part, but Quasar keeps asking to restart before using it (although it auto starts normally). May it have something to do with the fact that this version of Kodi does use another userdata path?
By default Kodi uses C:\Users\"YOURUSERNAME"\AppData\Roaming\Kodi but Win Store version uses
C:\Users\"YOURUSERNAME"\AppData\Local\Packages\XBMCFoundation.Kodi_4n2hpmxwrvr6p\LocalCache\Roaming\Kodi
Here is a Quasar log: quasar_log.txt
I'm having trouble making Quasar work on the Windows Store version of Kodi, as Sp4ik has provided a log I haven't but if you need it just ask and I will provide it.
Quasar makes no assumptions about the add-on's or the user's profile path, and gets the proper paths from Kodi, so that shouldn't be a problem. However it does look like the Windows Store is preventing Quasar from writing its own repository in the addons folder, but again that shouldn't cause the daemon to crash... Might want to stick to the non-Windows Store version of Kodi.
Wait.. you've got two quasar processes running now... Uninstall, make sure there are no leftover processes, and it's the log of when you're installing it that I need, although I'm pretty sure it'll look just like the one in #576. If so I think there's still hope to fix this issue sooner than later.
Here's another one that I uninstalled, restarted Kodi and reinstalled.
http://pastebin.com/fRAQ4zJS
- Still not working. Unable to properly install.
- It does work when you install Quasar in Kodi v16.1, disable automatic updates and exit. Then install Kodi v17 from the Windows Store.
Hello, I'm having the same issue, and as said it seems by reading my log file that quasar tries to create the repository in the "C:\Users[username]\AppData\Roaming\Kodi\addons" folder but access is denied, I think it is because addons are only allowed to do so in the "C:\Users[username]\AppData\Local\Packages\XBMCFoundation.Kodi_4n2hpmxwrvr6p\LocalCache\Roaming\Kodi\addons" folder (where every other repository, script and plugin, including the quasar one since it installs but isn't able to go on, are installed). Has there been any tryouts as to whether it would work to modify the destination folder in the quasar code or maybe if there is a downloadable quasar repository we could install it from it without the need of being autocreated by the addon? If you'll need any testing or I can be of any help I'm available :)
Hello,
I'm having the same problem. I think mirkorm is right. In the logfile it shows "panic: html/template: pattern matches no files: C:\Users\HomeTheater account\AppData\Roaming\Kodi\addons\plugin.video.quasar\resources\web\*.html"
The Kodi directory doesn't exist on this location when using the Windows store version.
http://pastebin.com/KRj1VugH
As I mentioned in my first comment, Quasar gets its profile path from Kodi and doesn't make assumptions about where it is installed. However, the repository installation kinda does, since it takes Quasar's path and tries to install itself in ... But if Kodi is telling us we're in AppData\Roaming\Kodi\addons, but that we're in fact in AppData\Local\Packages\..whateverthef***else, then it's obvious that we're getting f***ed here, and everything we'll try to do later on when trying to find our own files is going to fail. And I don't think we can work around this when seeing the randomly generated path we're into, so Kodi has to return the proper path in the first place, and everything should be just fine afterwards.
Since the kodi support has no e-mail address to write to I recently created a forum post without citing the quasar add-on by name, since they don't cover 3rd party add-ons in their custumer support, but nobody gave and answer yet (http://forum.kodi.tv/showthread.php?tid=307081)
Nicely done, and explains the issue very well. I thought of a workaround meanwhile: detecting our add-on path ourselves under Windows. I doubt Python will return the wrong one.
@elgatito I'm guessing we should do that before using the new getShortPath
I don't see any problems, why not detect 'current' directory on all OSs. Who knows whag we get, while we heavily depend on that path.
Is this suppose to work now? Because I still have the problem on Kodi from Windows store. I can paste my logs later today, if someone can help me solve this... I am using latest quasar version 0.9.78.
It's still an open issue as you can see.
I'm guessing this is gonna take a very long time or it will never happen. There are too many issues with store version, like writing to paths. I think it's too secure and restricted to to let a not "official" kodi addon run properly without making it extremely complex.
For example it used to work if I first installed Quasar on a normal version, then disable the updates for quasar (it couldn't install properly on the store version) and installed the store version. This no longer works because there was an update so that also the paths outside the app (library and temp download files) no longer worked.
I'm just a user of this great addon and I quited the store version some time ago now. Microsoft itself keeps screwing up by releasing "beta" software as stable software. So if you can avoid software that has something to do with Microsoft, I advice you to do so. Also in this case.
I was waiting on feedback after the last path change, so logs of the latest version would be really useful if we want to get this fixed at some point.
Last time I checked, every time I opened Windows Store's Kodi with quasar installed, it gave this access denied popup (http://imgur.com/a/D6HDy) and after clicking "ok" it opened Quasar's settings, and when I tried to open Quasar it said I needed to restart Kodi to make Quasar work but same thing happened after restarting. Concerning the log file, I noticed Quasar continuously tried to connect but it wasn't allowed, I already checked the firewall settings and everything was set to be allowed. I'm sorry I disappeared but I finally surrendered and installed the desktop version of Kodi and completely uninstalled the Store's version and now Quasar works like a charm. If it was me I'd try to make users download and install the Quasar repository and then install from there the video add-on and Burst just to completely remove the path problem and start on par with the other popular add-ons and if there would be any problems even there, troubleshooting from that point would be a step closer to the solution. I don't know maybe you already tried this but I hope my thought could be of some help :)
as a work around: open cmd terminal and run
cd %appdata%\Roaming
mklink /D Kodi %appdata%\Local\Packages\XBMCFoundation.Kodi_4n2hpmxwrvr6p\LocalCache\Roaming\Kodi
I'm seeing this error on Raspbian GNU/Linux 10 (buster) kodi --version 17.6 Debian package version: 2:17.6+dfsg1-4+b1 Media Center Kodi from Debian using plugin.video.quasar v0.9.78..
Where are these logs everyone keeps pasting?
