Install Google Chrome on Fedora 23/22, CentOS/RHEL 7.2

chrome-logo-smallThis guide explains howto install Google Chrome Web browser on Fedora 23/22/21/20/19/18 and CentOS/Red Hat (RHEL) 7.2. Best way to install and keep up-to-date with Google Chrome browser is use Google’s own YUM/DNF repository.

Currently it’s not possible to install Google Chrome on CentOS 6 / Red Hat (RHEL) 6 and Google Says Red Hat Enterprise Linux 6 Is Obsolete, but don’t worry, I write guide, howto install Chromium Web Browser on CentOS 6 / Red Hat (RHEL) 6.

Install Google Chrome on Fedora 23/22/21/20/19/18, CentOS 7.2, Red Hat (RHEL) 7.2

1. Change to root user.

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.

Run following command (copy & paste all lines to console) to create /etc/yum.repos.d/google-chrome.repo file:

3. Install Google Chrome with YUM

3.1 Install Google Chrome Stable Version

3.2 Install Google Chrome Beta Version

3.3 Install Google Chrome Unstable Version

Google Chrome Stable Running on CentOS 7 64-bit

Google Chrome Running on CentOS 7

Share this post

294 Comments

  1. Puzzled! Always your instructions perfect, but this time google-chrome-stable under Fedora 23 will only run as root. Have checked file permissions, etc. and they all seem ok. Am I missing something?

    Your help appreciated!

    Reply
    • Hi Bogo,

      Thanks!

      What you see in terminal if you try to run google-chrome as normal user?

      Reply
      • Hi

        Sorry for delay. Been away.

        I see nothing when I run “google-chrome” or “google-chrome-stable” in the terminal. And a ctl-C just takes me back to the prompt. Should I be looking for some error log somewhere?

        TIA

        Reply
        • yum install google-chrome-stable*

          I am on CentOS 7 and at the time of writing it installed :
          google-chrome-stable-48.0.2564.97-1.x86_64

          Add the wildcard and it will look for the most recent version to your install.

          Reply
          • Hi Obleeks,

            “yum install google-chrome-stable*” actually installs all packages which starts with google-chrome-stable not latest version. You get always latest version without wilcard.

            Reply
        • JR, still can’t run google-chrome on Fedora 23 despite removing and re-installing.

          I see nothing in the terminal: no response, I just exit via ctl-C.

          Any suggestions appreciated.

          TIA Bogo

          Reply
          • Hi Bogo,

            Could you post output of following command (example to http://pastebin.com) :

            I can setup exactly same machine and test is it working for me with same setup.

            Reply
        • Copy and paste these syntax onto your terminal but make sure it is running on root user:
          cat < /etc/yum.repos.d/google-chrome.repo
          [google-chrome]
          name=google-chrome – \$basearch
          baseurl=http://dl.google.com/linux/chrome/rpm/stable/\$basearch
          enabled=1
          gpgcheck=1
          gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
          EOF

          Then press enter

          At this point, you should be still at the root user. You can now type in:
          dnf install google-chrome-stable

          Reply
  2. another helpful post! thanks, works great on my Fedora 23 32-bit workstation. now I can do the kindle reader chrome add-on

    Reply
  3. Thanks for the effort of putting this up!

    Reply
  4. I run with no problem today as always with the latest stable under 64 bits F23.

    Bogo writes:
    Bogo on February 7, 2016 at 6:00 am

    Could it be a launcher issue?
    Bogo, because you use the word terminal may I ask if you try to start within an SSH session, or some terminal emulator, using a command line, or as I do from the Applications menu on the PC display?

    You issue MAY BE DUE to a Wayland idiosyncrasy. May I suggest to repeat your test by selecting an alternate display manager with the small wheel visible on the display when you are prompted for your login password?

    Reply
    • Thanks Jacques,

      I still can’t find any problem with Bogo setup. And I just write this using Chrome Beta on Fedora 23 and no problems at all.

      But you might be totally right and alternate display manager is good to try.

      Reply
      • Thanks Jacques & JR

        1. I have tried both from the menu and from terminal. The only way I can get it to run is as root from the terminal which is not satisfactory, obviously.

        2. Followed up your suggestion of a Wayland issue. I run Gnome 3 normally, so changed to Wayland and logged in. Chrome then runs as normal from the menu.

        Only problem with Wayland is that it is a little sluggish, and also there are times when I can’t log-in and have to revert to Gnome with X server.

        It would be good to have Chrome running under Fedora 23, X-server & Gnome 3. Frustrating to know that you guys can do it with the identical set-up. I don’t get the relationship between Chrome & Wayland & Gnome 3. Wayland wasn’t even in the picture until Jacques suggested it – it seems like a reverse relationship!

        Solution still eagerly sought! Thanks for your help in the meantime …

        Reply
        • Dear Bogo,

          Have you please tried to run Firefox (or at least one other browser) both as root and as regular user, and in all cases with X11 and with Wayland)? Faster more sophisticated tools exist, I know, but in your case I would start that way.

          My educated guess is that you gave a permission problem in some component of the X11 system.
          There is nothing sarcastic in the following, just my way to describe the situation.
          When you get a runny nose, it does not help to complain about the weather or heating the room where you stay. Better have your nose examined and eventually, for example if the liquid is not transparent, get some antibiotics.
          As far was a human being can be sure, I am sure that CHROME IS NOT TO BE BLAMED IN YOUR CASE.

          Don’t be angry at me please, I am trying to help you: the solution of your problem will come much faster from an F23 forum than from a Chrome forum. With a little bit of luck Firefox may well suffer from the same disease.

          Jacques

          Reply
          • Addendum

            To: moderator
            Please feel free to remove from my previous post whatever appears to you as excessively agressive.

            To: Bongo
            Here is how to start what I meant by faster tools:

            1-Do the following under the display manager which you wish to use by default, logged in as regular user

            2-Open an extra terminal (in addition to the one used to launch Chrome if you want to launch from a terminal)

            3-Before launching Chrome the way you like, enter the following command in the extra window (including answering the sudo prompt):
            sudo journalctl -f _COMM=gdm-x-session | tee myXorg.log

            4-Launch the browser

            5-Watch the extra window

            6-After exiting/killing the browser , hit CTRL-C in the extra window.

            7-If you seek extra help send file myXorg.log with your message

            Jacques

            Reply
  5. yum is depreciated, we should use dnf correct.

    Reply
    • Yes, YUM is deprecated on Fedora 23/22, but not older Fedora’s or CentOS/Red Hat 7.

      I’m not sure did you read this guide, because I have separated commands for F23/F22 (dnf) and older Fedora’s and CentOS/Red Hat 7 (yum).

      Feel free to tell us your correct way to use only dnf?

      Reply
      • I believe he was confused(as am I) that you added the repository to yum instead of dnf in step 2, and then installed it with dnf in step 3. Or is that the only way it should/can be done?

        Reply
        • Hi Person,

          This is how dnf works. Check https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrators_Guide/sec-Managing_DNF_Repositories.html

          Most important part:

          Adding a DNF Repository
          To define a new repository, you can either add a [repository] section to the /etc/dnf/dnf.conf file, or to a .repo file in the /etc/yum.repos.d/ directory. All files with the .repo file extension in this directory are read by DNF, and it is recommended to define your repositories here instead of in /etc/dnf/dnf.conf.

          So yes, you could define repository directly to /etc/dnf/dnf.conf, but it is recommended to define your repositories to .repo files in the /etc/yum.repos.d/ directory.

          Reply
          • I was just bit confused with dnf vs yum and the repos. Your explanation cleared that up. Thank you for the info.

            Reply
  6. I’m getting this error when I perform a dnf update:
    Failed to synchronize cache for repo ‘google-chrome’ from ‘http://dl.google.com/linux/chrome/rpm/stable/i386’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried, disabling.

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *