Hi I am trying to install Google Chrome from Software of Fedora. but it says ‘Unable to install Google Chrome: Cannot download google-chrome-stable-74.0.3729.131-1.x86-64.rpm: All mirrors were tried; Last error: Status code: 404 for http://dl.google.com/linux/chrome/rpm/stable/i386/google-chrome-stable-74.03729.131-1.x86_64.rpm’
Would be great if you described to us the way you installed it in the first place.
Have you tried the method the way described in the following link?
https://docs.fedoraproject.org/en-US/quick-docs/installing-chromium-or-google-chrome-browsers/
I have tried this in very first time
hi,
Try those commands in terminal:
1. Change to root user.
sudo -i
## OR ##
su -
2. Enable Google YUM repository
Note: Google Chrome Linux version doesn’t get any 32-bit (x86) updates and 32-bit repo is also removed. If you have 32-bit version installed, then you can use it, but you can’t get security updates or other updates anymore.
Fedora 30/29/28/27
dnf install fedora-workstation-repositories
dnf config-manager --set-enabled google-chrome
3. Install Google Chrome Stable Version
## Install Google Chrome Stable version ##
## Fedora 30/29/28/27 ##
dnf install google-chrome-stable
Regards
2 Likes
[root@localhost ~]# dnf install fedora-workstation-repositories
Fedora Modular 29 - x86_6 30 kB/s | 26 kB 00:00
Fedora Modular 29 - x86_6 35 kB/s | 23 kB 00:00
Fedora 29 - x86_64 - Upda 30 kB/s | 22 kB 00:00
Fedora 29 - x86_64 25 kB/s | 26 kB 00:01
Google Chrome 32-bit 11 kB/s | 1.4 kB 00:00
Failed to synchronize cache for repo 'google-chrome'
Ignoring repositories: google-chrome
Package fedora-workstation-repositories-29-1.fc29.noarch is already installed.
Dependencies resolved.
Nothing to do.
Complete!
Please provide the result of this command
dnf repolist -v
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.2.5
cachedir: /var/tmp/dnf-pizzapablo666-mqkla18e
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-cisco-openh264.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
repo: using cache for: fedora-modular
fedora-modular: using metadata from Thu 25 Oct 2018 02:22:05 +04.
repo: using cache for: updates-modular
updates-modular: using metadata from Tue 07 May 2019 18:19:09 +04.
repo: using cache for: updates
updates: using metadata from Thu 09 May 2019 06:59:45 +04.
repo: using cache for: fedora
fedora: using metadata from Thu 25 Oct 2018 02:20:15 +04.
repo: downloading from remote: google-chrome
error: Status code: 404 for http://dl.google.com/linux/chrome/rpm/stable/i386/repodata/repomd.xml (http://dl.google.com/linux/chrome/rpm/stable/i386/repodata/repomd.xml).
Google Chrome 32-bit 10 kB/s | 1.4 kB 00:00
Cannot download 'http://dl.google.com/linux/chrome/rpm/stable/i386': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried.
Failed to synchronize cache for repo 'google-chrome'
Ignoring repositories: google-chrome
Last metadata expiration check: 4:15:23 ago on Thu 09 May 2019 12:31:17 +04.
Completion plugin: Generating completion cache...
Completion plugin: Can't write completion cache: attempt to write a readonly database
Repo-id : fedora
Repo-name : Fedora 29 - x86_64
Repo-revision: 1540419615
Repo-updated : Thu 25 Oct 2018 02:20:15 +04
Repo-pkgs : 58,205
Repo-size : 69 G
Repo-metalink: https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64
Updated : Thu 09 May 2019 12:31:17 +04
Repo-baseurl : https://mirror.linux-ia64.org/fedora/linux/releases/29/Everything/x86_64/os/
: (144 more)
Repo-expire : 604,800 second(s) (last: Thu 09 May 2019
: 12:31:17 +04)
Repo-filename: /etc/yum.repos.d/fedora.repo
Repo-id : fedora-modular
Repo-name : Fedora Modular 29 - x86_64
Repo-revision: 1540419659
Repo-updated : Thu 25 Oct 2018 02:22:05 +04
Repo-pkgs : 8
Repo-size : 3.3 M
Repo-metalink: https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-29&arch=x86_64
Updated : Thu 09 May 2019 12:30:20 +04
Repo-baseurl : https://fedora.mirror.garr.it/fedora/linux/releases/29/Modular/x86_64/os/
: (146 more)
Repo-expire : 172,800 second(s) (last: Thu 09 May 2019
: 12:30:20 +04)
Repo-filename: /etc/yum.repos.d/fedora-modular.repo
Repo-id : updates
Repo-name : Fedora 29 - x86_64 - Updates
Repo-revision: 1557362367
Repo-updated : Thu 09 May 2019 06:59:45 +04
Repo-pkgs : 19,938
Repo-size : 31 G
Repo-metalink: https://mirrors.fedoraproject.org/metalink?repo=updates-released-f29&arch=x86_64
Updated : Thu 09 May 2019 12:30:30 +04
Repo-baseurl : http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/updates/29/Everything/x86_64/
: (113 more)
Repo-expire : 21,600 second(s) (last: Thu 09 May 2019
: 12:30:30 +04)
Repo-filename: /etc/yum.repos.d/fedora-updates.repo
Repo-id : updates-modular
Repo-name : Fedora Modular 29 - x86_64 - Updates
Repo-revision: 1557238678
Repo-updated : Tue 07 May 2019 18:19:09 +04
Repo-pkgs : 15
Repo-size : 13 M
Repo-metalink: https://mirrors.fedoraproject.org/metalink?repo=updates-released-modular-f29&arch=x86_64
Updated : Thu 09 May 2019 12:30:23 +04
Repo-baseurl : http://ftp.ntua.gr/pub/linux/fedora/linux/updates/29/Modular/x86_64/
: (125 more)
Repo-expire : 21,600 second(s) (last: Thu 09 May 2019
: 12:30:23 +04)
Repo-filename: /etc/yum.repos.d/fedora-updates-modular.repo
Total packages: 78,166
1 Like
Try these steps.
sudo rm /etc/yum.repos.d/google-chrome.reposudo dnf reinstall fedora-workstation-repositoriessudo dnf config-manager --set-enabled google-chromesudo dnf search google-chrome-stable --refresh
3 Likes
+1
Also: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/FoE6sL-p6oU
They do not provide 32 bit versions of Chrome any more. You aren’t on a 32bit system @parleedave so there’s no reason to look for a 32 bit build. Please use the standard version they provide just here: https://www.google.com/chrome/
Looking at the Fedora repositories
it seems that it is a 64 bit system.
Maybe he is using an old repository configuration file for Chrome.
This is the reason I was suggesting to remove such 32 bit repository and reinstall the fedora-workstation-repositories package.
1 Like
This worked thank you a lot!
1 Like
BTW seriously don’t install Chrome… Why would you… (no, that is no browser discussion)
If you want that browser, just install Chromium! It’s exactly the same (Google actually develops Chromium, adds some stuff and ships it as Google Chrome), just misses some proprietary parts (or tracking who knows) and Google branding from Google Chrome.
So there is no reason to add custom repos or so just for that. Chromium is available in the Fedora repos!
I have really no idea why so few people know they could just install Chromium and get exactly the same. Even on Linux many people try to install that Google-branded build of the same… 
1 Like
(that is no browser discussion)
Using GSuite, and at work I have to use it, I can see some differences. Sometimes Chromium eat a lot of CPU, while Chrome not. Sometimes Hangouts freezes using Chromium, while Chrome works like a charm. So there are some differences. This is only my experience.
For the rest you are right, there is no reason to use Chrome in place of Chromium.
And in fact I use Firefox. 
4 Likes
That’s why every linux distro has preinstalled Firefox in it.
I think some users prefer Chrome because it has flash player already installed. 
Kind Regards.
If that is true, that is either Google deliberately borking it’s FLOSS version, or just a bug… I mean, it’s the same code base, so a thing as this should not really happen. Very curious…
. Woah, Chrome still does this? 
I mean, despite that this is obviously a non-free component (which I thought Linux users could care about), it’s 2019 and flash should be dead for decades. (And no, you don’t need it for anything…) Actually IIRC Adobe will end support for it in 2020, so it will definitively be dead soon anyway.
2 Likes