- Package:
- webext-ublock-origin-chromium
- Source:
- webext-ublock-origin-chromium
- Submitter:
- Richard Lewis
- Date:
- 2025-06-10 15:07:01 UTC
- Severity:
- normal
Dear Maintainer, The latest upgrade of chromium considers the ublock plugin unsupported. I was able to re-enable following the instructions in a comment here: https://github.com/uBlockOrigin/uBlock-issues/issues/3563 ie enable: chrome://flags/#temporary-unexpire-flags-m133 Restart the browser, then disable: chrome://flags/#extension-manifest-v2-deprecation-warning chrome://flags/#extension-manifest-v2-deprecation-disabled chrome://flags/#extension-manifest-v2-deprecation-unsupported And enable: chrome://flags/#allow-legacy-mv2-extensions and restart the browser, -- apparently that will only work until June Is there a replacement planned?
I confirm this workaround works... I'm not sure there is a way to replace ublock-origin, given that manifest v2 is going away... Perhaps we need to have brave browser in Debian as an alternative?
For now, enabling Developer Mode in Chromium's Extensions Settings page also works. This is actually mentioned by the browser itself, you just need to pay attention and follow its instructions. Best, Ximin Pedro Ribeiro:
This package should be removed from trixie since it doesn't work without workarounds. As mentioned, these workarounds are only temporary anyway and will likely be irrelevant by release time. v2 is going away... The alternative for chromium is ublock-origin-lite however it's too late to get new packages into trixie as far as I know. Debian already offers an alternative browser, it's called Firefox, and there is already webext-ublock-origin-firefox working fine.
I think it makes more sense to keep webext-ublock-origin-chromium because a sensible workaround exists for now. Also there might be an effort to port ublock-origin to newer Chromium versions in a few months and then we could just upgrade it in stable via a point release. It would be more of a hassle if we had to re-introduce the binary package then again. That's correct. I have to look into ublock-origin-lite and if we want to bundle the sources with the normal ublock-origin or switch to it entirely or create a separate source package for it. That's something for the next release cycle. Right. webext-ublock-origin-firefox works fine and Firefox isn't a bad alternative either.