Open ibhagwan opened 5 months ago
Thanks!
This is very strange behavior as a restart should always install the pending new versions of extensions. I can't imagine what is causing this but I can think of 2 pretty far-fetched ideas:
chrome://restart
?You can also try disabling uBlock before installing the new version, then re-enabling it afterwards. I've seen this suggested as a way to avoid the restart.
chrome://restart
until the next updateThose permissions are probably normal, but you could compare to some other extensions you have installed and see if those files are also 600? I think 1 is more likely but frankly these are both just wild guesses.
I’ll explore more on the next update, any pointers what to look for? Potential debug log file I can enable?
I'm not sure since extension updates are handled by the browser and not this extension, there may be a log somewhere but it's beyond my knowledge.
I have the same problem (I'm on Arch Linux). Manual update (https://clients2.google.com/service/update2/crx?response=redirect&acceptformat=crx2,crx3&prodversion=999&x=id%3Dcjpalhdlnbpafiamejdnhcphjbkeiagm%26installsource%3Dondemand%26uc) (you need --extension-mime-request-handling=always-prompt-for-install
first) also doesn't work, so this might not be an extension bug
Can confirm this issue, restarting the browser fixes it, but if this could be resolved, it would be a great QoL improvement.
Hi and @ty for this great plugin!
This issue existed for a while across different versions of ungoogled-chromium along with different versions of the store plugin.
I am able to update all plugins by cliicking the store icon and then clocking the outdated plugin, but it fails with uBlock Origin , the updated will be downloaded, I get the
add <plugin>?
popup but the plugin isn't being replaced/reloaded after pressing "add extension" (even after browser restart).The only to update uBlock Origin is to remove the plugin and reinstall.