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/libz.so.1: no version information available (required by /usr/bin/google-chrome) /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /opt/google/chrome/chrome: /lib/libz.so.1: no version information available (required by /opt/google/chrome/chrome) /opt/google/chrome/chrome: /lib/libz.so.1: 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 20.0.1132.47
$ cat /etc/centos-release CentOS release 6.2 (Final)
$ uname -r 2.6.32-220.23.1.el6.centos.plus.i686
$ rpm -qa | grep zlib zlib-1.2.3-27.el6.i686
$ getenforce Disabled
[1]http://code.google.com/p/chromium/issues/detail?id=96988 [2]http://code.google.com/p/chromium/issues/detail?id=135150
Gary Trotcko wrote:
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/libz.so.1: no version information available (required by /usr/bin/google-chrome) /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /opt/google/chrome/chrome: /lib/libz.so.1: no version information available (required by /opt/google/chrome/chrome) /opt/google/chrome/chrome: /lib/libz.so.1: 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?
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.....
mark
mark
On Tue, Jul 3, 2012 at 5:37 PM, m.roth@5-cent.us 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:
On Tue, Jul 3, 2012 at 5:37 PM, m.roth@5-cent.us 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.
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.
mark
Hello Gary,
On Tue, 2012-07-03 at 21:03 +0300, Gary Trotcko wrote:
I wonder if I only user who came across this bug.
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.
Regards, Leonard.
On Tue, Jul 3, 2012 at 10:01 PM, Leonard den Ottolander leonard@den.ottolander.nl wrote:
Hello Gary,
On Tue, 2012-07-03 at 21:03 +0300, Gary Trotcko wrote:
I wonder if I only user who came across this bug.
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. -- Best Regards, Gary Trotcko
On 07/03/2012 02:03 PM, Gary Trotcko wrote:
I wonder if I only user who came across this bug.
What do you get when you run
ldd /opt/google/chrome/chrome
Gary Trotcko wrote:
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/libz.so.1: no version information available (required by /usr/bin/google-chrome) /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /opt/google/chrome/chrome: /lib/libz.so.1: no version information available (required by /opt/google/chrome/chrome) /opt/google/chrome/chrome: /lib/libz.so.1: no version information available (required by /opt/google/chrome/chrome)
I see the same warnings - but chrome runs fine.
The above are just warnings - I see them occasionally with other apps with other libs
For one explanation see:
http://stackoverflow.com/a/156387
James Pearson
On Wed, Jul 4, 2012 at 1:17 AM, James Pearson james-p@moving-picture.com wrote:
I see the same warnings - but chrome runs fine.
The above are just warnings - I see them occasionally with other apps with other libs
For one explanation see:
http://stackoverflow.com/a/156387
James Pearson
In my case Chrome hangs at boot time.
On 07/03/2012 09:21 AM, Gary Trotcko wrote:
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/libz.so.1: no version information available (required by /usr/bin/google-chrome) /usr/bin/google-chrome: /lib/libz.so.1: no version information available (required by /usr/bin/google-chrome) /opt/google/chrome/chrome: /lib/libz.so.1: no version information available (required by /opt/google/chrome/chrome) /opt/google/chrome/chrome: /lib/libz.so.1: 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 20.0.1132.47
$ cat /etc/centos-release CentOS release 6.2 (Final)
$ uname -r 2.6.32-220.23.1.el6.centos.plus.i686
$ rpm -qa | grep zlib zlib-1.2.3-27.el6.i686
$ getenforce Disabled
For what it's worth, I am running that version of chrome:
google-chrome-stable-20.0.1132.47-144678.x86_64
On x86_64 and I have no issues whatsoever.
I have:
zlib-1.2.3-27.el6.x86_64
that provides:
/lib64/libz.so.1
Make sure the zlib that you have provides /lib/libz.so.1
On Tue, Jul 10, 2012 at 12:48 PM, Johnny Hughes johnny@centos.org wrote:
For what it's worth, I am running that version of chrome:
google-chrome-stable-20.0.1132.47-144678.x86_64
On x86_64 and I have no issues whatsoever.
I have:
zlib-1.2.3-27.el6.x86_64
that provides:
/lib64/libz.so.1
Make sure the zlib that you have provides /lib/libz.so.1
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.
The upgrade to CentOS 6.3 has fixed the issue with my google-chrome. Thanks a lot for all.
-
Gary Trotcko -
Giovanni Tirloni -
James Pearson -
Johnny Hughes -
Leonard den Ottolander -
m.roth＠5-cent.us -
Steve Clark