PSA: Google Chrome drops support for 32 bit and Mint 13

[xenopeek]

Google Chrome developers have announced that from early March 2016 they will no longer support 32 bit builds of Google Chrome on Linux or any build of Google Chrome on Linux Mint 13 (Ubuntu 12.04) specifically.

Those of you that have a 32 bit installation of Linux Mint (or any installation of Linux Mint 13) are out of luck. You could continue to use Google Chrome beyond early March 2016 but will no longer receive updates that fix security issues. Hence Linux Mint recommends you do not continue to use Google Chrome unless you have a 64 bit installation of Linux Mint 17 or newer.

You can read their post here: https://groups.google.com/a/chromium.or ... oE6sL-p6oU

FAQ

Q: What about Chromium?
A: Chromium will continue to be supported on 32 bit. Note however that the PepperFlash and Widevine plugins that you can use with Chromium (to have the latest Adobe Flash and to watch Netflix or Amazon Prime) come from the Google Chrome package and will thus no longer be supported for 32 bit Chromium.

Q: What about Firefox?
A: Users of 32 bit Firefox that are using Fresh Player plugin to use the PepperFlash plugin are similarly affected.

Q: So what Adobe Flash plugin can I use for 32 bit installations of Linux Mint 17 or newer?
A: As it stands it looks like you can only use the Adobe Flash plugin from Adobe (11.2 release). This is installed by default Linux Mint 17. Mind that Adobe will discontinue support for that from March/April 2017 (source).

Q: So what Adobe Flash plugin can I use for Linux Mint 13?
A: As it stands it looks like you can only use the Adobe Flash plugin from Adobe (11.2 release). This is installed by default Linux Mint 13. Both Adobe Flash and Linux Mint 13 will reach end of support from March/April 2017.

Q: How do I check my Linux Mint version and whether I'm using 32 bit or 64 bit?
A: If you're unsure about either, open the terminal application from your menu and type this command (capital S): inxi -S. This will show you whether you are using 32 bit or 64 bit and what version of Linux Mint.

Q: How do I remove Google Chrome?
A: You can remove Google Chrome from Software Manager. The package to remove is called google-chrome-stable (other possibilities are google-chrome-beta or google-chrome-unstable, if you have opted to install those).

You'll have to manually remove the Google Chrome software repository. To do so open Software Sources (found in the Edit menu of Software Manager). For Linux Mint 13 on the "Other Software" tab highlight the "dl.google.com/linux/chrome/..." line and remove it. For Linux Mint 17 on the "Additional Repositories" tab highlight the "Google" entry that has the "dl.google.com/linux/chrome/..." line and remove it.

If you're not using any of the other Google software repositories you can also remove the Google authentication key from Software Sources. For Linux Mint 13 on the "Authentication" tab highlight the "Google, Inc." line and remove it. For Linux Mint 17 on the "Authentication keys" tab highlight the "Google, Inc." line and remove it.

Q: How do I check which Adobe Flash plugin I'm using?
A: This works for any browser. Go to https://www.adobe.com/software/flash/about/ and see the small "Version Information" box which shows which version is installed and used for this browser. If the version is higher than 11.2.x, you're using the PepperFlash plugin from Google Chrome. If the version is 11.2.x, you're using the Adobe Flash plugin from Adobe (the default on Linux Mint 13 and 17). If the "Version Information" box doesn't show up, most likely you have disabled Adobe Flash in this browser or you don't have a Adobe Flash plugin installed that this browser can use. Check by going to chrome://flash for Chromium.

Q: How do I remove PepperFlash plugin?
A: There are two steps to removing the PepperFlash plugin. Step 1 is to uninstall the PepperFlash plugin itself. Open a terminal and run this command to remove it:

Code: Select all

sudo update-pepperflashplugin-nonfree --uninstall

It won't give you any output unless there is an error. To check you no longer have the PepperFlash plugin installed run:

Code: Select all

sudo update-pepperflashplugin-nonfree --status

Step 2 is to uninstall the pepperFlash plugin installer package. Either from Software Manager remove the package pepperflashplugin-nonfree or while you're at the terminal do it with:

Code: Select all

apt purge pepperflashplugin-nonfree

[ZakGordon]

That is a bit rude of google is it not?

What with all the issues around Flash (Adobe) over recent years, removing the one stable, decent performing and secure platform seems very mean. A lot of people pick a Linux distro to run on old/not powerful hardware and google is in effect telling them to upgrade their hardware if they want to use a fully functional browser on the internet?!

I hope you guys are all ready for all the threads about this stuff, and trying to get youtube (etc) to work under Mint etc!!

As an aside i do not know what has been happening in Silicon Valley over the last few years, but first MS (with the changes in Windows 8 and 10) and now Google, but it seems there is a really mean spirit going around the elite tech companies currently, which is very dissapointing imho.

[BEeK]

That is a bit rude of google is it not?

In my opinion, it is not.

First, you should also know they are dropping support for Vista and XP as well. It is nothing linux exclusive.

And come on, 32 bit is getting obsolete. And they've been holding it for many, many years.

If you want to browse on your old computer, use an old browser. It makes sense.

If your computer is newer than 10 years. Then you should not have a problem.

[Moem]

Users of 32 bit Firefox that are using Fresh Player plugin to use the PepperFlash plugin are similarly affected.

And other browsers, I assume. Bummer.

[eatenimpinia]

Google Chrome developers have announced that from early March 2016 they will no longer support 32 bit builds of Google Chrome on Linux or any build of Google Chrome on Linux Mint 13 (Ubuntu 12.04) specifically....

Q: How do I remove Google Chrome?
A: You can remove Google Chrome from Software Manager. The package to remove is called google-chrome-stable (other possibilities are google-chrome-beta or google-chrome-unstable, if you have opted to install those).

You'll have to manually remove the Google Chrome software repository. To do so open Software Sources (found in the Edit menu of Software Manager). For Linux Mint 13 on the "Other Software" tab highlight the "dl.google.com/linux/chrome/..." line and remove it. For Linux Mint 17 on the "Additional Repositories" tab highlight the "Google" entry that has the "dl.google.com/linux/chrome/..." line and remove it.

If you're not using any of the other Google software repositories you can also remove the Google authentication key from Software Sources. For Linux Mint 13 on the "Authentication" tab highlight the "Google, Inc." line and remove it. For Linux Mint 17 on the "Authentication keys" tab highlight the "Google, Inc." line and remove it.

Since yesterday, I've been getting a "Could not download all repository indexes" error in Update Manager for Google Chrome:

Code: Select all

Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/Release  Unable to find expected entry 'main/binary-i386/Packages' in Release file (Wrong sources.list entry or malformed file)
Some index files failed to download. They have been ignored, or old ones used instead.

To me, that looks like it's having trouble with the stable release of Google Chrome. But, I don't have that (Software Manager confirms it). I'm running the 64-bit beta of Google Chrome.

An inxi -S and inxi -r gives the following:

Code: Select all

dave@dave-mint ~ $ inxi -S
System:    Host: dave-mint Kernel: 3.19.0-49-generic x86_64 (64 bit)
           Desktop: Cinnamon 2.8.6  Distro: Linux Mint 17.3 Rosa
dave@dave-mint ~ $ inxi -r
Repos:     Active apt sources in file: /etc/apt/sources.list.d/google-chrome-beta.list
           deb http://dl.google.com/linux/chrome/deb/ stable main
           Active apt sources in file: /etc/apt/sources.list.d/jtaylor-keepass-trusty.list
           deb-src http://ppa.launchpad.net/jtaylor/keepass/ubuntu trusty main
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://mirrors.kernel.org/linuxmint-packages rosa main upstream import
           deb http://extra.linuxmint.com rosa main
           deb http://mirrors.us.kernel.org/ubuntu trusty main restricted universe multiverse
           deb http://mirrors.us.kernel.org/ubuntu trusty-updates main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ trusty-security main restricted universe multiverse
           deb http://archive.canonical.com/ubuntu/ trusty partner
           Active apt sources in file: /etc/apt/sources.list.d/spideroakone.list
           deb http://APT.spideroak.com/ubuntu-spideroak-hardy/ release restricted
           Active apt sources in file: /etc/apt/sources.list.d/steam.list
           deb [arch=amd64,i386] http://repo.steampowered.com/steam/ precise steam
           deb-src [arch=amd64,i386] http://repo.steampowered.com/steam/ precise steam

I'm assuming I'm getting the error because the repository is used for all versions. But, in my ignorance, I don't know. The quote from the OP says I need to remove the Chrome repository (and authentication key if not using any other Chrome products). But, do I remove the repository if I'm using the Chrome beta? If I do, will it somehow magically re-populate with the correct repository or do I have to manually add it?

EDIT: I see in

https://groups.google.com/a/chromium.or ... oE6sL-p6oU

that I can supposedly fix this by changing the line:

deb http://dl.google.com/linux/chrome/deb/ stable main

in source.list to

deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

But, the person who posted that doesn't provide any source/rationale for that. Basically, it looks like he's saying I need to pre-pend that [arch=amd64] to the deb. But, I don't know how to confirm that source. Any suggestions on that?

[Shryp]

A little more info for the above post.

https://www.reddit.com/r/chrome/comment ... _to_fetch/

I used the suggestion from one of the comments of going to the edit sources link in the update manager to edit the URL and it looks to be working for me.

[samriggs]

A little more info for the above post.

https://www.reddit.com/r/chrome/comment ... _to_fetch/

I used the suggestion from one of the comments of going to the edit sources link in the update manager to edit the URL and it looks to be working for me.

Thanks for the link Shryp I forgot to add it in the post, much appreciated.
Sam

[phd21]

Hi Everyone,

I just read your post and the good replies to it. Here are my thoughts on this as well.

Thank you "xenopeek" and others for this post and the good replies.

Here is another web link regarding this:

Fix `Failed To Fetch` Google Chrome Repository After Google Dropped Support For Its Browser On Linux 32bit
http://www.webupd8.org/2016/03/fix-fail ... ome_3.html

Note: You do not have to stop using Google Chrome, and or to remove it, but it will not receive any more updates, including security updates, so that is a security risk... If you continue to use Chrome, I would definitely use "firejail" to sandbox it.

Hope this helps ...

[eatenimpinia]

Well, yesterday I "fixed" this by editing my sources in Update Manager to include that [arch=amd64] bit. That worked for a whole day. This morning, something seems to have "corrected" the repository path by removing the [arch=amd64]. So, I'm back to having that error.

In one of the threads floating around the forum about this, someone mentioned that uninstalling Google Chrome, removing the repository, and re-installing Chrome permanently fixed the issue. I'll see if I can find that thread and confirm the process. I wonder if this is a Google issue, a Linux issue, or a Mint issue. This really shouldn't be happening because Google stopped supporting 32-bit.

EDIT: Before uninstalling/re-installing Chrome, I guess I'll try the following:

Code: Select all

sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list"
sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/opt/google/chrome/cron/google-chrome"

That's from the link in phd21's post just above this one.

[Cosmo.]

If you continue to use Chrome, I would definitely use "firejail" to sandbox it.

This is as bad as the idea of numerous Windows-users who believe, that an AV or a program like Sandboxie would be replacement for an outdated OS or an outdated browser. More to read.

[eatenimpinia]

...Before uninstalling/re-installing Chrome, I guess I'll try the following:

Code: Select all

sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list"
sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/opt/google/chrome/cron/google-chrome"

I had to change those commands a bit since I'm running the Google Chrome beta releases and not the mainstream stuff:

Code: Select all

sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome-beta.list"
sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/opt/google/chrome-beta/cron/google-chrome-beta"

We'll see what happens.

[powerwagon75]

For whatever reason, the code lines that have been shown in the line code sections didn't work for me. I did copy/paste from two different locations just in case I wasn't seeing a text error, but it didn't help.

However, from terminal, manually editing the two files as root, and adding the "[arch=amd64]" to the lines just after "deb" worked just fine. Update ran without errors. (running 64 bit Chrome)

[MtnDewManiac]

This morning, something seems to have "corrected" the repository path by removing the [arch=amd64].

It definitely corrected things on MY end. I had been waiting to see whether or not the "issue with mintUpdate" icon would correct itself or not... Today, I noticed that I had the normal "you have updates available" icon again. I checked and there is now an update (which wasn't there before) from version 48.something to version 49.something. So my guess is that people - who have a [i[supported[/i] version of Chrome - who chose to do nothing in hopes that the system would straighten itself out... have been rewarded with success, and now do not need to do anything (other than the standard update routine).

Regards,
MDM

[ZakGordon]

That is a bit rude of google is it not?

In my opinion, it is not.

First, you should also know they are dropping support for Vista and XP as well. It is nothing linux exclusive.

And come on, 32 bit is getting obsolete. And they've been holding it for many, many years.

If you want to browse on your old computer, use an old browser. It makes sense.

If your computer is newer than 10 years. Then you should not have a problem.

What about people not in western europe/usa (first world economies etc) who only have access to what we would consider old hardware? And certainly using an outdated browser that does not get security updates etc is never a good idea.

Like i said this seems like a really mean spirited move, elitist in it's assumption that everyone should be on 64bit (when 32bit functions fine, as does 16bit etc). This attitude is certainly spreading, and i'm not a fan of it, not everyone has access to (or can afford) the latest technologies.

[BEeK]

What about people not in western europe/usa (first world economies etc) who only have access to what we would consider old hardware?

Well, I am not in Europe/USA. I'm from South America, and my monthly income is ~$220.

Like i said this seems like a really mean spirited move, elitist in it's assumption that everyone should be on 64bit (when 32bit functions fine, as does 16bit etc). This attitude is certainly spreading, and i'm not a fan of it, not everyone has access to (or can afford) the latest technologies.

My desktop computer was quite cheap, I'm running a $40 processor. It supports "64 bit".

"64 bit" has advantages and disadvantages, its advantages are starting to matter more as software evolve and open new possibilities.

It is not an iPhone or a PlayStation 4 price tag.

[MtnDewManiac]

Like i said this seems like a really mean spirited move

???

Google WAS paying for the development of a piece of 32-bit software. The powers-that-be at Google have decided to stop spending that money.

If I give you a sandwich today, give you a sandwich tomorrow, and give you a sandwich the day after that... But then decide on the following morning that I will now keep my money and spend it on something besides feeding YOU sandwiches...

Am I suddenly mean-spirited, lofl? How about if I had never given you any sandwiches in the first place? Would that make me more or less mean-spirited than if I had been allowing you to eat from my larder and then stopped letting you do so? And what if I offered you a sandwich, but you decided that you'd rather use someone else's brow-- I mean go freeload off someone else? Would that make YOU mean-spirited? After all, I already made the sandwich. And I cut the crust off the way you like .

Are you planning on assuming Google's complete development/maintenance cost for a 32-bit Chrome? If so, and you make the offer (along with the stated willingness to deposit a suitable amount of money in some sort of non-revocable account, in order to guarantee that you won't yank the money back) to Google, and Google STILL refuses to continue developing a 32-bit version of its browser...

That still won't make it - or the people who control it - "mean-spirited."

Here, go eat a sandwich:

Code: Select all

http://www.opera.com/download/guide/?os=linux-i386

Regards,
MDM

[amethyst_igor]

1. Chrome dropped support for Windows XP already - old news
2. Firefox works great on Windows XP and on all versions of Linux. So, why use Chrome at all?
3. Chromium exists as another alternative to Chrome, and it is in the default Software Manager.

What Chrome does or doesn't do never interested me much. I can do everything I need in Firefox, faster. And then there is an entire universe of Firefox add-ons to customize my browser the way I want. In Chrome, there is less.

[Cosmo.]

BTW: Chrome support will in the next month (April 16) also end for Vista, although this system still is supported by MS for another year.

[amethyst_igor]

I just delete Internet Explorer and Chrome whenever I see it on an old machine. Using older versions of browsers is just asking for trouble. Firefox is the only way forward.

[Moem]

It's not like those are the only browsers in the world... I don't use Chrome or Firefox. The world is full of options.