After Last Update Google-chrome No Runs Anymore

Home » CentOS » After Last Update Google-chrome No Runs Anymore
CentOS 17 Comments

Hi all. I’ve updated google-chrome to recent version and it gets unbooted, when I fired google-chrome up I got messages like these:
/usr/bin/google-chrome: /lib/ no version information available (required by /usr/bin/google-chrome)
/usr/bin/google-chrome: /lib/ no version information available (required by /usr/bin/google-chrome)
/opt/google/chrome/chrome: /lib/ no version information available (required by /opt/google/chrome/chrome)
/opt/google/chrome/chrome: /lib/ no version information available (required by /opt/google/chrome/chrome)

I’m familiar with selinux bug[1] and my issue is similar for this, but selinux in my system is completely disabled. I’ve opened issue at chrome’s bug tracker[2] but not recived conceived response yet. Is anyone here who experienced the same problem?

$ google-chrome –version

$ cat /etc/CentOS-release
CentOS release 6.2 (Final)

$ uname -r

$ rpm -qa | grep zlib zlib-1.2.3-27.el6.i686

$ getenforce


17 thoughts on - After Last Update Google-chrome No Runs Anymore

  • Gary Trotcko wrote:

    libz has nothing to do with selinux. From rpm -qi:
    Description :
    Zlib is a general-purpose, patent-free, lossless data compression library which is used by many different programs.

    Sounds like a library problem to me: either chrome doesn’t like the std.
    libz provided in the CentOS Zlib package, or it’s missing, or…..



  • What have I got to do? Have I got to report a bug to CentOS bug tracker? Or…. In OpenSuse the same version of Chrome works fine.

  • Gary Trotcko wrote:

    CentOS is pretty much a clone of RHEL. With this issue, either it’s a problem with upstream, as we say, or it’s a problem with chrome, or you’ve installed a version of chrome that’s not for RHEL and clones.


  • Hello Gary,

    And I wonder if you read what Mark Roth suggested. Did you install a version for RHEL/CentOS or did you accidentally install a version for another flavour of Linux? And if you did install a build for RHEL/CentOS
    did you get one for the right version of CentOS?

    If answering the above questions does not solve your problem you are probably better off taking your issue to a Chrome specific mailing list.


  • I installed google-chrome at CentOS 6.0 and it has beeen working fine for year since that moment until now. I asumed this version was correct considering the number of successful updates.

  • $ ldd /opt/google/chrome/chrome
    /opt/google/chrome/chrome: /lib/ no version information available (required by /opt/google/chrome/chrome)
    /opt/google/chrome/chrome: /lib/ no version information available (required by /opt/google/chrome/chrome) => (0x002d2000) => /usr/lib/ (0x004da000) => /usr/lib/ (0x00221000) => /usr/lib/ (0x002b8000) => /usr/lib/ (0x00405000) => /lib/ (0x00638000) => /lib/ (0x008c3000) => /lib/ (0x009bb000) => /lib/ (0x00970000) => /lib/ (0x00c9c000) => /usr/lib/ (0xb34e4000) => /usr/lib/ (0x00110000) => /usr/lib/ (0x00365000) => /usr/lib/ (0x001c5000) => /usr/lib/ (0x001e4000) => /usr/lib/ (0x00ea3000) => /usr/lib/ (0x0022a000) => /usr/lib/ (0x00416000) => /usr/lib/ (0x00273000) => /usr/lib/ (0x0068d000) => /usr/lib/ (0x00a00000) => /usr/lib/ (0x001f0000) => /lib/ (0x00f55000) => /lib/ (0x00acf000) => /lib/ (0x002d3000) => /lib/ (0x002bb000) => /usr/lib/ (0x002ee000) => /lib/ (0x00384000) => /usr/lib/ (0x00354000) => /usr/lib/ (0x00b29000) => /lib/ (0xb33f5000) => /usr/lib/ (0x00f97000) => /lib/ (0x007c6000) => not found => /lib/ (0x00328000) => /lib/ (0x003cb000) => /usr/lib/ (0xb3307000) => /lib/ (0x004ae000) => /lib/ (0x00b74000) => /lib/ (0xb3176000)
    /lib/ (0x0066d000) => /usr/lib/ (0x003dc000) => /lib/ (0xb30c5000) => /usr/lib/ (0x00f5c000) => /lib/ (0x00a4c000) => /usr/lib/ (0x0021b000) => /usr/lib/ (0x002a8000) => /usr/lib/ (0x00c74000) => /usr/lib/ (0x00b4e000) => /usr/lib/ (0x0021e000) => /usr/lib/ (0x00641000) => /usr/lib/ (0xb305a000) => /lib/ (0x0062a000) => /usr/lib/ (0xb2ffd000) => /lib/ (0xb2fbd000) => /lib/ (0xb2ee7000) => /lib/ (0x00842000) => /lib/ (0x00357000) => /usr/lib/ (0xb2e3e000) => /usr/lib/ (0x00612000) => /usr/lib/ (0xb2e2c000) => /lib/ (0xb2dfc000) => /lib/ (0x0090c000) => /usr/lib/ (0x002cf000) => /lib/ (0xb2de2000) => /lib/ (0xb2dc2000) => /lib/ (0x00a83000) => /lib/ (0x00e75000) => /usr/lib/ (0x00a50000) => /lib/ (0xb2d72000)

  • Hello Gary,

    Not sure if this is related, but it is the only thing sticking out:

    bzip2-libs only provides and, not libbz2.sos.1.0. bzip2-devel doesn’t provide it either, nor does any other package.

    If you haven’t installed bzip2-libs install it. If you still see that
    “libbz2 not found” try (assuming you’re on i386):
    # cd /lib
    # ln -s

    and see if that makes a difference.

    Since CentOS uses an unaltered SRPM for bzip2 you can be pretty sure Red
    Hat does not provide that link either. Which means that dependency is a
    “chromism”, i.e. a bug in Chrome, possibly due to a build system with a modified bzip2.

    You could also try booting a stock kernel, not a CentOSplus one.


  • The bzip2-libs is installed at my system but didn’t exist so I’ve created symlink and it hasn’t effect:
    $ ldd /opt/google/chrome/chrome | grep libbz
    /opt/google/chrome/chrome: /lib/ no version information available (required by /opt/google/chrome/chrome)
    /opt/google/chrome/chrome: /lib/ no version information available (required by /opt/google/chrome/chrome) => /lib/ (0x001af000)

  • Hello Gary,

    Ok, so adding that symlink does not make Chrome happy to the point where it starts working? Still that requirement is a bug and suggests that google uses an unclean (i.e. patched) build system, not a stock RHEL or

    As people pointed out that libz warning in itself is probably harmless.

    All that is left is to repeat my advise: If the suggestions given here do not fix your issue you might want to take it to a Chrome specific list. If you do take your issue there, please mention the bogus requirement on and point out that that link is *not*
    available on stock CentOS 6 (and in all likeliness neither on RHEL 6)


  • Leonard den Ottolander wrote:

    The google-chrome-stable RPM creates the symlink
    /opt/google/chrome/ to /lib/ – and the google-chrome wrapper sets LD_LIBRARY_PATH to include /opt/google/chrome
    – so chrome finds without a problem.

    i.e. there isn’t a problem with either or

    If chrome is not starting, then there is probably another issue – you could try moving the preferences/profile out of the way – e.g.

    cd $HOME/.config
    mv google-chrome

    and try again

    If that doesn’t help, try running chrome through strace and see if that gives any clues …

    James Pearson

  • For what it’s worth, I am running that version of chrome:


    On x86_64 and I have no issues whatsoever.

    I have:


    that provides:


    Make sure the zlib that you have provides /lib/

  • Same here.

    $ cat /etc/redhat-release Red Hat Enterprise Linux Workstation release 6.3 (Santiago)
    $ uname -a Linux gtirloni 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 20 01:32:12 EDT 2012
    x86_64 x86_64 x86_64 GNU/Linux

    I would change that /opt/google/chrome/google-chrome shell script and make chrome run through strace to see what’s going on.