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
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
