Install Google Chrome on Fedora 28/27, CentOS/RHEL 7.5 - Comment Page: 12

This guide explains howto install Google Chrome Web browser on Fedora 28/27/26/25 and CentOS/Red Hat (RHEL) 7.5. Best way to install and keep up-to-date with Google Chrome browser is use Google's own YUM/DNF repository. Install Google Chrome on Fedora 28/27/26/25, CentOS 7.5, Red Hat (RHEL) 7.5 [inttf_post_ad1] 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 28/27 dnf install...

346 comments on “Install Google Chrome on Fedora 28/27, CentOS/RHEL 7.5 - Comment Page: 12

1 10 11 12
    1. Worked well for me on Fedora 25 at China Guangzhou. Thank you!

      Reply
    2. Trying to install google-chrome-unstable on Operating System: CentOS Linux 7 (Core) and I am getting the following error (any help would be appericated!):

      [[email protected] ~]# yum install google-chrome-unstable
      Loaded plugins: fastestmirror, langpacks, universal-hooks
      Loading mirror speeds from cached hostfile
      * EA4: 74.50.120.123
      * cpanel-addons-production-feed: 74.50.120.123
      * base: mirror.jax.hugeserver.com
      * epel: mirror.nodesdirect.com
      * extras: centos.mirror.lstn.net
      * ius: archive.linux.duke.edu
      * updates: centos.aol.com
      Resolving Dependencies
      –> Running transaction check
      —> Package google-chrome-unstable.x86_64 0:61.0.3163.13-1 will be installed
      –> Processing Dependency: libc.so.6(GLIBC_2.18)(64bit) for package: google-chrome-unstable-61.0.3163.13-1.x86_64
      –> Finished Dependency Resolution
      Error: Package: google-chrome-unstable-61.0.3163.13-1.x86_64 (google-chrome)
      Requires: libc.so.6(GLIBC_2.18)(64bit)
      You could try using –skip-broken to work around the problem
      You could try running: rpm -Va –nofiles –nodigest

      Reply
      • Hi Anthony,

        This is true, I just tested google-chrome-unstable on CentOS 7 and yes it won’t install (google-chrome-stable and google-chrome-beta works normally). Hopefully this doesn’t mean that Google Chrome 61 and above (stable and beta releases), won’t work anymore on CentOS 7.

        Reply
    3. Installing Google Chrome in Fedora 26 from Google website works just fine with Wayland. Installing it from command line does not work with Wayland.

      Reply
      • Hi JW,

        It’s same file!

        Downloaded from Google’s rpm repo:

        
        md5sum google-chrome-stable-60.0.3112.101-1.x86_64.rpm 
        75466e3b2859651ff16b0ad9566077d9  google-chrome-stable-60.0.3112.101-1.x86_64.rpm
        

        Downloaded from Google’s website:

        
        md5sum google-chrome-stable_current_x86_64.rpm 
        75466e3b2859651ff16b0ad9566077d9  google-chrome-stable_current_x86_64.rpm
        

        So doesn’t matter where you download stable version.

        I just tested this with two clean Fedora 26 Workstation VM. Installed chrome stable from Google’s website and another from Google’s repo and both failed with Wayland.

        Reply
    4. If you are getting a message when you try to install Chrome like this:

      Failed to synchronize cache for repo ‘google-chrome’, disabling.

      Simply get rid of the backslashes in front of $basearch from the bit above that you put in the /etc/yum.repos.d/google-chrome.repo file.

      Reply
    5. This is what i’m getting upon trying step 3.3…..Fedora 27

      Failed to synchronize cache for repo ‘google-chrome’, disabling.
      Last metadata expiration check: 0:43:06 ago on Sat 16 Dec 2017 05:24:51 PM IST.
      No match for argument: google-chrome-stable
      Error: Unable to find a match

      Please help

      Reply
      • Hi kankit,

        I just tested this and google chrome repo is working normally. Run following command first:

        
        dnf clean all
        

        Then try installation again.

        Reply
    6. Does not work for fedora 27 Security Labs spin.

      key can’t be checked

      Reply
      • Hello ileana,

        I just updated this guide. Try following repo file instaead.

        cat < < EOF > /etc/yum.repos.d/google-chrome.repo
        [google-chrome]
        name=google-chrome - x86_64
        baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
        enabled=1
        gpgcheck=1
        gpgkey=https://dl.google.com/linux/linux_signing_key.pub
        EOF

        Tested this and should work. Now it’s ok use also hard coded x86_64 parts, because only 64-bit version is available.

        Reply
    7. [chrome]
      name=google-chrome
      baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
      enabled=1
      gpgcheck=1
      gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub

      use this repo ^ for fedora 27 if the other doesn’t work

      Reply
      • Hi nukerock terra,

        Just checked Google’s own RPM and they use following repo (for Fedora, CentOS, RHEL):

        [google-chrome]
        name=google-chrome
        baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
        enabled=1
        gpgcheck=1
        gpgkey=https://dl.google.com/linux/linux_signing_key.pub
        
        Reply
    8. it worked for me by adding this repo

      cat < /etc/yum.repos.d/google-chrome.repo
      [google-chrome]
      name=google-chrome
      baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64/
      gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub
      enabled=1
      gpgcheck=1
      EOF

      then

      # yum install google-chrome-stable

      Reply
      • Hello dante,

        Have to ask, how this is different than what is described on step 2.?

        Only difference is gpgkey url, but both https://dl-ssl.google.com/linux/linux_signing_key.pub and https://dl.google.com/linux/linux_signing_key.pub loads exactly same file:

        
        cd /tmp
        
        wget https://dl.google.com/linux/linux_signing_key.pub
        ...
         - ‘linux_signing_key.pub’ saved [8038/8038]
        
        wget https://dl-ssl.google.com/linux/linux_signing_key.pub
        ...
         - ‘linux_signing_key.pub.1’ saved [8038/8038]
        
        md5sum linux_signing_key.pub*
        1d5b6f105f7e63312651cb9e7f424905  linux_signing_key.pub
        1d5b6f105f7e63312651cb9e7f424905  linux_signing_key.pub.1
        

        So I don’t understand what is the problem?

        Reply
    9. Tried installing Google Chrome 66 (stable, as of 2018-04-24)

      “`
      $ sudo dnf install google-chrome-stable
      Last metadata expiration check: 0:41:40 ago on Tue 24 Apr 2018 01:06:51 PM PDT.
      Error:
      Problem: conflicting requests
      – nothing provides libappindicator3.so.1()(64bit) needed by google-chrome-stable-66.0.3359.117-1.x86_64

      “`

      – does anyone know how to manually select an older version of google-chrome-stable to download/install? (e.g. Chrome 65, or Chrome 64)?

      Reply
      • Hello Mike,

        dnf whatprovides */libappindicator3.so.1
        Last metadata expiration check: 0:05:42 ago ...
        libappindicator-gtk3-12.10.0-16.fc27.x86_64 : Application indicators library - GTK 3
        Repo        : @System
        Matched from:
        Filename    : /usr/lib64/libappindicator3.so.1
        
        libappindicator-gtk3-12.10.0-16.fc27.i686 : Application indicators library - GTK 3
        Repo        : fedora
        Matched from:
        Filename    : /usr/lib/libappindicator3.so.1
        
        libappindicator-gtk3-12.10.0-16.fc27.x86_64 : Application indicators library - GTK 3
        Repo        : fedora
        Matched from:
        Filename    : /usr/lib64/libappindicator3.so.1

        Try first run (root user):

        dnf clean all
        
        dnf install google-chrome-stable
        Reply
        • Thanks JR, will try it out and report back.

          Reply
          • JR- Looks like no joy, still. Thanks anyways, for the suggestion.

            Reply
            • Hi Mike,

              Could you post output of following command:

              dnf whatprovides */libappindicator3.so.1
              Reply
              • Hi JR,

                I get the following output:

                “`
                $ dnf whatprovides */libappindicator3.so.1
                Last metadata expiration check: 0:00:05 ago on Fri 27 Apr 2018 11:15:08 AM PDT.
                Error: No Matches found
                “`

                Reply
                • Hi JR,

                  Solved the problem- it turns out that I had inadvertently disabled the main `fedora` repository a while back while troubleshooting a different package update problem. Re-enabling the `fedora` repo allowed me to install Google Chrome properly.

                  Thanks for the help!

                  Reply
                  • Excellent, nice to hear that you got it working!

                    Reply
    10. Can’t find google-chrome-stable
      Set chrome repo, but package not found:
      yum search google-chrome
      Loaded plugins: fastestmirror
      =========================================================================================== N/S matched: google-chrome ============================================================================================
      google-chrome-beta.x86_64 : Google Chrome (beta)
      google-chrome-unstable.x86_64 : Google Chrome (unstable)

      Name and summary matches only, use “search all” for everything.

      only beta and unstable present

      Reply
      • Hi Oleg,

        Maybe you should just run ‘dnf clean all’ and test again. It should be there:

        dnf list google-chrome\*
        Installed Packages
        google-chrome-stable.x86_64             66.0.3359.139-1           @google-chrome
        Available Packages
        google-chrome-beta.x86_64               67.0.3396.18-1            google-chrome 
        google-chrome-unstable.x86_64           68.0.3409.2-1             google-chrome
        Reply
    11. Rather than encourage people to change to root, please use sudo. The command to create the repo file is:

      $ cat < /dev/null
      > [google-chrome]
      > name=google-chrome
      > baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
      > enabled=1
      > gpgcheck=1
      > gpgkey=https://dl.google.com/linux/linux_signing_key.pub
      > EOF

      Reply
      • Grrr, damn cut-and-paste, should be

        $ cat < /dev/null
        > [google-chrome]
        > name=google-chrome
        > baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
        > enabled=1
        > gpgcheck=1
        > gpgkey=https://dl.google.com/linux/linux_signing_key.pub
        > EOF

        Reply
        • Nope, it’s the commenting platform which kills less thans :-(

          Reply
          • Hi vk5tu,

            I’m not totally sure about your command, but have to say that sudo is not more secure than root user, of course you can limit sudo commands, but if you use ALL setting on sudoers file, then you can run any command using sudo. I can’t assume that this guide reader even have sudo installed or configured. I personally prefer changing root if I run multiple commands. Actually sudo is even more dangerous, because “hacker” can gain root access just hacking user account, if you don’t have sudo installed and use even different passwords for user and root account, then hacker have to hack two passwords. Unfortunately Ubuntu users have many times sudo obsession, before Ubuntu sudo was very rarely used.

            Reply
    12. Sorry if this has been said already…I’m on a phone:

      In F28 all you have to do is install the package ‘fedora-workstation-repositories’. Then edit /etc/yum.repos.d/google-chrome.repo.

      Set ‘enable=’ to 1

      Reply
      • Hi Elijah,

        I don’t know which one is easier, but both works on Fedora 28.

        Reply
    13. Excellent guide! However, on Fedora 28, the google-chrome repo seems already to be present, but not enabled. So instead of overwriting it, one could just edit the file and change `enabled=0` to 1.

      Reply
      • Hi Dmitri,

        You have to have fedora-workstation-repositories package installed, then repo file exists and then you can enable it modifying repo file directly or using dnf config-manager.

        Reply
1 10 11 12

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Close