For the second time now, I've just run
apt upgrade and had this happen:
[...] Setting up google-chrome-stable (48.0.2564.116-1) ... update-alternatives: using /usr/bin/google-chrome-stable to provide /usr/bin/x-www-browser (x-www-browser) in auto mode [...]
I am pulling chrome with
deb http://dl.google.com/linux/chrome/deb/ stable main . My understanding of apt is a but shaky but generally isn't this the type of action which should only happen when first installing a package, or when using
dpkg reconfigure? It's extremely annoying and feels un-apty that I have to reset my preferred browser every time I
After the upgrade, this is what
update-alternatives is showing me:
$ update-alternatives --config x-www-browser There are 3 choices for the alternative x-www-browser (providing /usr/bin/x-www-browser). Selection Path Priority Status ------------------------------------------------------------ * 0 /usr/bin/google-chrome-stable 200 auto mode 1 /usr/bin/chromium 40 manual mode 2 /usr/bin/google-chrome-stable 200 manual mode 3 /usr/bin/iceweasel 70 manual mode Press enter to keep the current choice[*], or type selection number:
I find this table rather confusing, but thanks to this question I believe I understand the first (
0) entry is just used to select "auto" mode, and the listed binary indicates which choice will be used. The thing is, I'm 99% sure I used update-alternatives to switch this back to my preferred browser (iceweasel) after the last upgrade, so it should have been in "manual mode".
x-www-browser was certainly opening iceweasel before this upgrade.
Is the output of
apt upgrade indicating I was somehow mistaken and this was already in auto mode, even though it was opening iceweasel? Or is this the result of bad practices on the part of the chrome maintainers, and it's resetting to auto mode on every upgrade?