The newest Chromium in Debian sid disables remote extension loading by default. This has the effect of disabling extensions en masse. I'm not sure what the reasoning is, but it's damn inconvenient.
It's claimed that one way to get the old behavior back is to add
--enable-remote-extensionsto the list of flags in
/etc/chromium.d/default-flags. This will affect all users on the system, and the file could be overwritten by an upgrade. In addition, until I know better what's behind the change, I'd really like to apply the change only to my account, not to all users.I did this by adding:
# fix latest Debian Chromium disabling remote extensions
export CHROMIUM_FLAGS=$CHROMIUM_FLAGS" --enable-remote-extensions"~/.profile. Be sure to log out and back in to experience the change.
2 comments:
Another workaround is to edit the launcher you're using to open Chromium, just to add the flag to the end, like so:
/usr/bin/chromium %U --enable-remote-extensions
Then, you could even have two separate launchers, one with and one without extensions, if you're so inclined.
Thanks, Winn. I use this technique to add the --force-device-scale-factor flag to work around a different Chromium bug. I edit /usr/share/applications/chromium.desktop and add the flag there. It's kinda of a PITA to put the change back in every upgrade (I'm on sid), but it seems to be the least PITA fix, esp. if there are multiple users on the machine.
Post a Comment