Sonarr version (exact version): Version 2.0.0.3565 Mono version (if Sonarr is not running on Windows): 3.10.0-0xamarin2 OS: Linux Mint 17.3 ((Debug logs)): http://pastebin.com/jR1FqCNv (Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here) Description of issue:
I turned my PC on after about a year of not using it. Everything was working for sonarr last time I used the PC. I was initially running Linux Mint 17.1 (possibly 17.2) 64-bit, and started using sonarr right away.
The system log showed sonarr running correctly and it was grabbing nzbs from the indexers for all the missed shows. However, the GUI wouldn’t load (stuck at the initial loading circles). I assumed it wasn’t loading because it was under stress searching for all the missed shows.
I then updated from Firefox 42 to Firefox 51, completed all system software updates (mono version doesn’t appear to have changed, running 3.10.0-0xamarin2), upgraded to Mint 17.3 and rebooted the PC.
The system sonarr process log shows sonarr working correctly. It starts and has updated all shows and is no longer searching for missed episodes. It cycles through the RSS sync correctly.
But the loading screen still won’t load the GUI.
I’ve rebooted and restarted Firefox in safe mode, disabling all addons, but no dice. Sonarr is doing the same thing in Opera as well.
F12 network inspector shows sonarr trying to grab various CSS local files…
I see a few requests that Sonarr doesn’t have and I’m not sure we ever included, unless those requests are coming from something else it seems odd.
Which browser are you using?
Have you tried clearing the browser cache/history?
Have you tried a different browser?
I’m using Firefox 51.0.1… Linux Mint 17.3 kernel 4.0.4… I tried with and without add-ons… and also tried Opera 12.16… Yeap, cleared cache/history and everything… Its very odd, the actual daemon is working fine… it just completed a show refresh…
local.DOM storage was enabled as the default, but a new cookie program (self-destructing cookies, replacing the previous cookie monster) I was trying out needed to have cookies enabled in the Firefox options. Of course, restarting without add-ons enabled wouldn’t fix the problem, since cookies were globally disabled from the previous Cookie Monster extension…