On Tue, Jul 3, 2012 at 10:33 PM, Steve Clark sclark@netwolves.com wrote:
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
$ ldd /opt/google/chrome/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) linux-gate.so.1 => (0x002d2000) libX11.so.6 => /usr/lib/libX11.so.6 (0x004da000) libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00221000) libXss.so.1 => /usr/lib/libXss.so.1 (0x002b8000) libXext.so.6 => /usr/lib/libXext.so.6 (0x00405000) librt.so.1 => /lib/librt.so.1 (0x00638000) libdl.so.2 => /lib/libdl.so.2 (0x008c3000) libgobject-2.0.so.0 => /lib/libgobject-2.0.so.0 (0x009bb000) libgthread-2.0.so.0 => /lib/libgthread-2.0.so.0 (0x00970000) libglib-2.0.so.0 => /lib/libglib-2.0.so.0 (0x00c9c000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb34e4000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00110000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00365000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x001c5000) libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0x001e4000) libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00ea3000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x0022a000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00416000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00273000) libnss3.so => /usr/lib/libnss3.so (0x0068d000) libnssutil3.so => /usr/lib/libnssutil3.so (0x00a00000) libsmime3.so => /usr/lib/libsmime3.so (0x001f0000) libplc4.so => /lib/libplc4.so (0x00f55000) libnspr4.so => /lib/libnspr4.so (0x00acf000) libpthread.so.0 => /lib/libpthread.so.0 (0x002d3000) libz.so.1 => /lib/libz.so.1 (0x002bb000) libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0x002ee000) libdbus-1.so.3 => /lib/libdbus-1.so.3 (0x00384000) libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00354000) libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00b29000) libasound.so.2 => /lib/libasound.so.2 (0xb33f5000) libcups.so.2 => /usr/lib/libcups.so.2 (0x00f97000) libgcrypt.so.11 => /lib/libgcrypt.so.11 (0x007c6000) libbz2.so.1.0 => not found libexpat.so.1 => /lib/libexpat.so.1 (0x00328000) libudev.so.0 => /lib/libudev.so.0 (0x003cb000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb3307000) libm.so.6 => /lib/libm.so.6 (0x004ae000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00b74000) libc.so.6 => /lib/libc.so.6 (0xb3176000) /lib/ld-linux.so.2 (0x0066d000) libxcb.so.1 => /usr/lib/libxcb.so.1 (0x003dc000) libgio-2.0.so.0 => /lib/libgio-2.0.so.0 (0xb30c5000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00f5c000) libgmodule-2.0.so.0 => /lib/libgmodule-2.0.so.0 (0x00a4c000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x0021b000) libXi.so.6 => /usr/lib/libXi.so.6 (0x002a8000) libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00c74000) libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00b4e000) libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x0021e000) libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00641000) libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb305a000) libplds4.so => /lib/libplds4.so (0x0062a000) libORBit-2.so.0 => /usr/lib/libORBit-2.so.0 (0xb2ffd000) libgssapi_krb5.so.2 => /lib/libgssapi_krb5.so.2 (0xb2fbd000) libkrb5.so.3 => /lib/libkrb5.so.3 (0xb2ee7000) libk5crypto.so.3 => /lib/libk5crypto.so.3 (0x00842000) libcom_err.so.2 => /lib/libcom_err.so.2 (0x00357000) libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0xb2e3e000) libavahi-common.so.3 => /usr/lib/libavahi-common.so.3 (0x00612000) libavahi-client.so.3 => /usr/lib/libavahi-client.so.3 (0xb2e2c000) libcrypt.so.1 => /lib/libcrypt.so.1 (0xb2dfc000) libgpg-error.so.0 => /lib/libgpg-error.so.0 (0x0090c000) libXau.so.6 => /usr/lib/libXau.so.6 (0x002cf000) libresolv.so.2 => /lib/libresolv.so.2 (0xb2de2000) libselinux.so.1 => /lib/libselinux.so.1 (0xb2dc2000) libkrb5support.so.0 => /lib/libkrb5support.so.0 (0x00a83000) libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00e75000) libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0x00a50000) libfreebl3.so => /lib/libfreebl3.so (0xb2d72000)
Hello Gary,
Not sure if this is related, but it is the only thing sticking out:
On Wed, 2012-07-04 at 01:24 +0300, Gary Trotcko wrote:
libbz2.so.1.0 => not found
bzip2-libs only provides libbz2.so.1 and libbz2.so.1.0.4, 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 libbz2.so.1.0.4 libbz2.so.1.0
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.
Regards, Leonard.
On Wed, Jul 4, 2012 at 2:17 AM, Leonard den Ottolander leonard@den.ottolander.nl wrote:
Hello Gary,
Not sure if this is related, but it is the only thing sticking out:
On Wed, 2012-07-04 at 01:24 +0300, Gary Trotcko wrote:
libbz2.so.1.0 => not foundbzip2-libs only provides libbz2.so.1 and libbz2.so.1.0.4, 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 libbz2.so.1.0.4 libbz2.so.1.0
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 libbz2.so.1.0 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/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) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x001af000)
Hello Gary,
On Wed, 2012-07-04 at 11:46 +0300, Gary Trotcko wrote:
The bzip2-libs is installed at my system but libbz2.so.1.0 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/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) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x001af000)
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 CentOS.
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 libbz2.so.1.0 and point out that that link is *not* available on stock CentOS 6 (and in all likeliness neither on RHEL 6) systems.
Regards, Leonard.
Leonard den Ottolander wrote:
Hello Gary,
On Wed, 2012-07-04 at 11:46 +0300, Gary Trotcko wrote:
The bzip2-libs is installed at my system but libbz2.so.1.0 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/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) libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x001af000)
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 CentOS.
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 libbz2.so.1.0 and point out that that link is *not* available on stock CentOS 6 (and in all likeliness neither on RHEL 6) systems.
The google-chrome-stable RPM creates the symlink /opt/google/chrome/libbz2.so.1.0 to /lib/libbz2.so.1 - and the google-chrome wrapper sets LD_LIBRARY_PATH to include /opt/google/chrome - so chrome finds libbz2.so.1.0 without a problem.
i.e. there isn't a problem with either libbz2.so.1.0 or libz.so.1
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 google-chrome.save
and try again
If that doesn't help, try running chrome through strace and see if that gives any clues ...
James Pearson
-
Gary Trotcko -
James Pearson -
Leonard den Ottolander