Google Chrome 58 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. Get your own self-hosted blog with a Free Domain at ($3.95/month).
  4. Become a Supporter - Make a contribution via PayPal
  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...

310 Responses

  1. alok says:

    i have recentally installed chrome on centos 6.8 , but unable to open it . plz help

  2. Cyril says:

    I ran successfully the update statement:
    sudo yum update google-chrome-stable
    and
    yum info google-chrome-stable =>
    Installed Packages
    Name : google-chrome-stable
    Arch : x86_64
    Version : 56.0.2924.87
    Release : 1
    Size : 171 M
    Repo : installed

    However when I start Google and goes to the About tab, I still have the previous version:
    Version 53.0.2785.113 (64-bit)

    Any idea why?

  3. Jeeva says:

    Is there a way to install previous chrome version (say, chrome 55) ?

    • Ravi Saive says:

      @Jeeva,

      I don’t think its possible to install older versions of Chrome, try to search for RPMS or DEBS for your Linux distribution and see..

  4. Geo Camposano says:

    I’ve been trying to get chromedriver working to handle browser testing for my web apps on a Centos 6.8 setup running through Docker and have just been getting timeout issues with Lloyd’s script.

    While everything installs fine without error, I realized that running google-chrome just gives me an “Illegal Instruction” error and I’m guessing that is what’s preventing chromedriver from working properly. Any reason why?

  5. Bharathiraja says:

    Hi,

    Thanks for the script and i successfully installed chrome in redhat 6.8 and working well.

  6. jmc says:

    Works perfectly fine, installed Google Chrome in my Linux box without any errors. Many thanks for this. You saved my week..:)

  7. keops says:

    How can i run as root in fedora, please help me!!

    • Ravi Saive says:

      @Keops,

      To run Google Chrome as root, you need to open and edit the file /usr/bin/google-chrome as follows:

      exec < /dev/null 
      exec > >(exec cat)
      exec 2> >(exec cat >&2)
      # Note: exec -a below is a bashism.
      exec -a "$0" "$HERE/chrome"  "$PROFILE_DIRECTORY_FLAG" \
      "$@
      

      Change the above lines with following ones:

      exec < /dev/null 
      exec > >(exec cat)
      exec 2> >(exec cat >&2)
      # Note: exec -a below is a bashism.
      exec -a "$0" "$HERE/chrome"  "$PROFILE_DIRECTORY_FLAG" \
      "$@" --user-data-dir
      
  8. sasidaran s says:

    # yum install google-chrome-stable
    Getting this error
    Error: Package: google-chrome-stable-55.0.2883.87-1.x86_64 (google-chrome)
    Requires: libstdc++.so.6(GLIBCXX_3.4.18)(64bit)
    Error: Package: google-chrome-stable-55.0.2883.87-1.x86_64 (google-chrome)
    Requires: libstdc++.so.6(GLIBCXX_3.4.15)(64bit)
    Error: Package: google-chrome-stable-55.0.2883.87-1.x86_64 (google-chrome)
    Requires: libstdc++.so.6(GLIBCXX_3.4.14)(64bit)

    https://rpmfind.net/linux/rpm2html/search.php?query=libstdc%2B%2B.so.6%28GLIBCXX_3.4.18%29&submit=Search+…&system=centos+7&arch=

    This site is too not working i am using centos 7 help

  9. Sophia says:

    Hi. I’m on CentOS 6.8 with kernel version 2.6.32-642.11.1.el6.i686 and running Richard Lloyd’s script gives me the following:

    “ERROR: Unsupported architecture (i686) – aborted”

    As of last March does Chrome only support x86_64 and not i686? Does this mean I’m out of luck? I’m currently using Firefox 45 (the latest available on Yum) and it’s far from suitable for web development purposes in 2016.

    • Ravi Saive says:

      @Sophia,

      Yes, Google stopped support for i386 architecture, only 64-bit systems supported. So, unfortunately, you have to install 64-bit CentOS to get latest Chrome or stick with Firefox..

    • It’s unfortunate that the latest Firefox (now using GTK+3 if you download it from Mozilla’s site) and Chrome don’t work out-of-the-box on CentOS 6. As you say, yes Firefox ESR does work, but it’s many versions behind what the general population uses (I bet 99% of Firefox users don’t know the ESR version exists because it’s never promoted by Mozilla) and RHEL/CentOS will have a conundrum when the next ESR comes out – they might have to try to force it to stay on GTK+2 somehow!

      It’s a little surprising you’re running CentOS 6 on 32-bit – it must be creakingly old hardware you’re running it on (I’ve been on 64-bit since 2005). I dropped 32-bit support with my script within days of Google pulling their 32-bit repository and, no, I don’t want my script run against old versions of Chrome (e.g. an old 32-bit version) because that’s a security risk.

      FYI, I just released version 7.51 of my script today as an early Xmas present. Nothing new special in it – the main thing was a rebuild of libstdc++.so.6 using the latest gcc 6.3.0 that’s just come out.

      • Sophia says:

        Thanks for the reply!

        Through a series of unfortunate events, my laptop died and I salvaged the only desktop I could find lying around at work that didn’t require me to do a clean install: my boss’s old server that hadn’t even been booted for five years. My desire to not lose development days led to some poor judgment and of course two weeks later that box wasn’t booting, initially due to installing Oracle JDK8, and then due to an issue with OpenVPN I couldn’t troubleshoot since I wasn’t the one who built the firewall.

        So finally forced into the clean install I knew was inevitable and should have just done from the beginning I decided it was best to switch to Debian rather than upgrading to CentOS 7 as the former seems to have more support for bleeding edge dev tools (although I’ll still need to either switch to testing or backport many to stable). After spending a couple days troubleshooting hardware issues, I was amazed at the difference between Debian with Gnome vs. CentOS with KDE. It feels like having an assistant doing everything for me!

        Anyway, just wanted to say this blog has been really helpful. Really appreciate all you do, Ravi.

Got something to say? Join the discussion.

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