Yesterday we began to remember how Google Chrome ended 32-bit support on Linux systems, on Ubuntu 12.04 LTS and on Debian 7. This is not only causing sequelae on 32-bit machines that have run out of support, but also on 64-bit Linux computers with Google Chrome, giving a curious error.
The error is that when checking system updates, Google Chrome check both 32 and 64 bitsSince the 32-bit ones were removed, I get an error message that says the following.
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.
In Christian this means that there is an error in the i386 (32-bit) packages and that they will not be downloaded. This error does nothing (64-bit ones are downloaded), however, yes it emits an annoying error window every time we tell the browser to check for updates.
I imagine Google releases some kind of patch that fixes this bug, but we don't know how long it will take. The good news is that is it possible to fix this error using Linux command line and typing the following command (it is an example for Ubuntu and the apt package manager, if you use Debian and want to install chrome remember to change the sudo to a su at the beginning and then the command without the sudo).
sudo sed -i -e 's/deb http/deb [arch=amd64] http/' "/etc/apt/sources.list.d/google-chrome.list"
The command we have entered means that we are giving the order to only use the 64-bit repository, ignoring the i386 repository, thus, the Google Chrome error is over.
This error makes us reflect on the little attention that Google Chrome makes to Linux users, neglecting little things like these. If Google continues like this, it is going to lose a significant share of users with glitches like this.
Thank you very much I just got that error :)
I also solve it, but I did many more steps:
1) I opened a terminal and put in it "sudo nano -w /etc/apt/sources.list.d/google-chrome.list"
2) in the line «deb http://dl.google.com/linux/chrome/deb/ stable main »add« [arch = amd64] »getting:
"Deb [arch = amd64] http://dl.google.com/linux/chrome/deb/ stable main »
3) save the changes and update the repositories with "sudo apt-get update"
How badly they treat those of us who use chrome on GNU / Linux
The google-chrome.list file is regenerated with each update, therefore it is necessary to execute the command after each update of chrome (while we wait for a definitive solution from Google).
Greetings.
helps
cataclysm @ cataclysm-HP-Mini-1103: ~ $ sudo sed -i -e 's / deb http / deb [arch = amd64] http /' «/etc/apt/sources.list.d/google-chrome.list »
sed: cannot read /etc/apt/sources.list.d/google-chrome.list: File or directory does not exist
It does not appear in Arch, I suppose it is typical of other distros.
I'm going to test if I get this error. I have it as a fourth browser.
First Firefox, second Chromium, third Konqueror, fourth Chrome
Thanks for the solution :)
Thank you, very good contribution.
I deleted the repository and nothing comes out anymore I hope that what ise is not wrong
Fabricio, but I'm not wrong, that way Chrome won't be able to update from now on. You should uninstall it completely, download the official installer, and install it clean again.
Great, it worked for me. I hadn't realized it and I had that problem. Thanks!
Tell the truth Google does it on purpose because it does not do it to windows you can use it in 32-bit 64-bit versions, it is a mockery for those who use linux systems.
It tells me that it cannot be read because there is no file or directory, and I copy all the sudo
I get this
W: GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures could not be verified because their public key is not available: NO_PUBKEY A040830F7FAC5991 NO_PUBKEY 1397BC53640DB551
W: The repository "http://dl.google.com/linux/chrome/deb stable Release" is not signed.
N: The data in a repository like this cannot be authenticated and therefore its use is potentially dangerous.
N: See the apt-secure (8) man page for details on creating repositories and configuring users.
N: Omitting the use of the configured file "main / binary-i386 / Packages" since the repository "http://dl.google.com/linux/chrome/deb stable InRelease" does not support the "i386" architecture
and when i run sudo it comes out this
cataclysm @ cataclysm-HP-Mini-1103: ~ $ sudo sed -i -e 's / deb http / deb [arch = amd64] http /' «/etc/apt/sources.list.d/google-chrome.list »
sed: cannot read /etc/apt/sources.list.d/google-chrome.list: File or directory does not exist
helps
when i run sudo it tells me this
cataclysm @ cataclysm-HP-Mini-1103: ~ $ sudo sed -i -e 's / deb http / deb [arch = amd64] http /' «/etc/apt/sources.list.d/google-chrome.list »
sed: cannot read /etc/apt/sources.list.d/google-chrome.list: File or directory does not exist
I get this
cataclysm @ cataclysm-HP-Mini-1103: ~ $ sudo sed -i -e 's / deb http / deb [arch = amd64] http /' «/etc/apt/sources.list.d/google-chrome.list »
sed: cannot read /etc/apt/sources.list.d/google-chrome.list: File or directory does not exist
cataclysm @ cataclysm-HP-Mini-1103: ~ $ sudo sed -i -e 's / deb http / deb [arch = amd64] http /' «/etc/apt/sources.list.d/google-chrome.list »
sed: cannot read /etc/apt/sources.list.d/google-chrome.list: File or directory does not exist
what do I do?
Hi, the .list file has another name, you change google-chrome.list to google.list, and it works. Greetings.
I installed Chromium, which, for me, covers all the needs. I have Ubuntu 21.04 and it works perfectly.