Google Chrome 54 Released – Install on RHEL/CentOS 7/6 and Fedora 25-20

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Use our Linode referral link if you plan to buy VPS (it starts at only $10/month).
  4. Support us via PayPal donate - Make a Donation
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

Ravi Saive

I am Ravi Saive, creator of TecMint. A Computer Geek and Linux Guru who loves to share tricks and tips on Internet. Most Of My Servers runs on Open Source Platform called Linux. Follow Me: Twitter, Facebook and Google+

Your name can also be listed here. Got a tip? Submit it here to become an TecMint author.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

284 Responses

  1. elvin says:

    Running proof of transaction
    -> Package google-chrome-stable.x86_64 0: 54.0.2840.100-1 will be installed
    -> Processing Dependencies: libstdc ++. So.6 (GLIBCXX_3.4.18) (64bit) for the package: google-chrome-stable-54.0.2840.100-1.x86_64
    -> Resolved dependency resolution
    Error: Package: google-chrome-stable-54.0.2840.100-1.x86_64 (google-chrome)
    You need: libstdc ++ .so.6 (GLIBCXX_3.4.18) (64bit)

  2. Prateek Joshi says:

    [root@localhost ~]# yum info google-chrom-stable
    Loaded plugins: langpacks, product-id, subscription-manager
    This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
    Repository ‘prateek’ is missing name in configuration, using id
    google-chrome | 10 kB 00:00:00
    http://d1.google.com/linux/chrome/rpm/stable/%24basesearch/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for google-chrome: Damaged repomd.xml file
    Trying other mirror.

    One of the configured repositories failed (google-chrome),
    and yum doesn’t have enough cached data to continue. At this point the only
    safe thing yum can do is fail. There are a few ways to work “fix” this:

    1. Contact the upstream for the repository and get them to fix the problem.

    2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

    3. Disable the repository, so yum won’t use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    –enablerepo for temporary usage:

    yum-config-manager –disable google-chrome

    4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

    yum-config-manager –save –setopt=google-chrome.skip_if_unavailable=true

    failure: repodata/repomd.xml from google-chrome: [Errno 256] No more mirrors to try.
    http://d1.google.com/linux/chrome/rpm/stable/$basesearch/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for google-chrome: Damaged repomd.xml file

    getting this error please help me out with the best possible solution

    • Ravi Saive says:

      @Prateek,

      I think you’ve mis-spelled the repository, its actually dl.google.com not d1, you should add following lines to /etc/yum.repos.d/google-chrome.repo file.

      [google-chrome]
      name=google-chrome
      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
      

      Now you will able to install Google Chrome without any errors..

  3. Unca Alby says:

    BE WARNED! The URL in the instructions LOOK LIKE D1 (Dee One) but it’s actually DL (Dee Ell).
    E.g. d1.google.com WON’T work, but dl.google.com WILL. (notice the difference?)

Got something to say? Join the discussion.

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

Join Over 300K+ Linux Users
  1. 177,942
  2. 8,310
  3. 37,548

Are you subscribed?