Google Chrome

dc_eros · 06-01-2010, 11:12 PM

Hi slackers,

I upgraded my google chrome which was version 4 to version 5 using packages I got from slackbuilds. The dependencies don't have updates so I don't upgrade them (only chrome). It builds and installs.

However, when i launch it, it simply does not open. Opening via terminal reveals an error:

Code:

/usr/bin/google-chrome: error while loading shared libraries: libnss3.so.1d: cannot open shared object file: No such file or directory

What do I miss? Using slack 13.1 here.

TIA

bathory · 06-02-2010, 12:22 AM

Hi,

I don't know about the slackbuilds chrome package, but you miss some symlinks. You can make them by hand:

Code:

ln -s /usr/lib/libnss3.so /usr/lib/libnss3.so.1d
ln -s /usr/lib/libnssutil3.so /usr/lib/libnssutil3.so.1d
ln -s /usr/lib/libsmime3.so /usr/lib/libsmime3.so.1d
ln -s /usr/lib/libssl3.so /usr/lib/libssl3.so.1d
ln -s /usr/lib/libplds4.so /usr/lib/libplds4.so.0d
ln -s /usr/lib/libplc4.so /usr/lib/libplc4.so.0d
ln -s /usr/lib/libnspr4.so /usr/lib/libnspr4.so.0d

If you're using a 64bit Slack replace /usr/lib with /usr/lib64

Regards

dc_eros · 06-02-2010, 12:55 AM

Ummm... That's a lot. Okay I'll take note on that. Got to save that list somewhere.

Thank you very much.

Alien Bob · 06-02-2010, 02:47 AM

Those missing files are not called "libnss3.so.1d" and such... the error message is actually two sentences and the dot marks the end of sentence one. The second sentence starts with "ld:"

So, you are actually missing the file libnss3.so which is provided by the seamonkey-solibs package. You will find that package in the "L" package directory. Installing that package will add a line to your library loader (ld) configuration file /etc/ld.so.conf like this:

Code:

/usr/lib64/seamonkey

Eric

dc_eros · 06-02-2010, 02:55 AM

Here is the screenshot: http://www.flickr.com/photos/1105939...31671/sizes/l/

I'm using 32 bit. Okay, I'll check it out. I still have those packages at home. Thanks

bathory · 06-02-2010, 03:06 AM

OP is right. chrome is looking for those libraries having a 1d and 0d extension:

Code:

ldd /opt/google/chrome/chrome|grep "[0|1]d"
        libnss3.so.1d => /usr/local/lib/libnss3.so.1d (0xb6f36000)
        libnssutil3.so.1d => /usr/local/lib/libnssutil3.so.1d (0xb6f22000)
        libsmime3.so.1d => /usr/local/lib/libsmime3.so.1d (0xb6f03000)
        libplds4.so.0d => /usr/local/lib/libplds4.so.0d (0xb6f00000)
        libplc4.so.0d => /usr/local/lib/libplc4.so.0d (0xb6efc000)
        libnspr4.so.0d => /usr/local/lib/libnspr4.so.0d (0xb6eca000)

disturbed1 · 06-02-2010, 04:10 AM

The SlackBuild has code for the library links

Code:

# We need bits of Moz, do this as dynamically as possible:
MISSING_LIBS=$(ldd opt/google/chrome/chrome | grep "not found" | cut -d\  -f1 | xargs)
for MLIB in $MISSING_LIBS ; do
  ln -s /usr/lib${LIBDIRSUFFIX}/seamonkey/${MLIB%.?d} opt/google/chrome/$MLIB
done

Even after that, chrome still does not find the needed libraries.

Here's the dirty hack I use.

Code:

#!/bin/bash
 
sed -i 's,libnss3.so.1d,libnss3.so\x00\x00\x00,g;
	s,libnssutil3.so.1d,libnssutil3.so\x00\x00\x00,g;
	s,libsmime3.so.1d,libsmime3.so\x00\x00\x00,g;
	s,libssl3.so.1d,libssl3.so\x00\x00\x00,g;
	s,libplds4.so.0d,libplds4.so\x00\x00\x00,g;
	s,libplc4.so.0d,libplc4.so\x00\x00\x00,g;
	s,libnspr4.so.0d,libnspr4.so\x00\x00\x00,g;' chrome

rmjohnso · 06-02-2010, 05:00 AM

I've had a similar problem. The mozilla-nss build from SlackBuilds seems to work for me:

http://slackbuilds.org/repository/13...m/mozilla-nss/

smoooth103 · 06-02-2010, 12:34 PM

I also had the same issue. I couldn't figure out why it was referencing a /usr/lib64/ when I am on 32 bit.

I changed the symlinks by hand and had them reference existing mozilla nss libraries.

rmjohnso · 06-02-2010, 04:04 PM

Quote:

Originally Posted by Alien Bob

Those missing files are not called "libnss3.so.1d" and such... the error message is actually two sentences and the dot marks the end of sentence one. The second sentence starts with "ld:"

So, you are actually missing the file libnss3.so which is provided by the seamonkey-solibs package. You will find that package in the "L" package directory. Installing that package will add a line to your library loader (ld) configuration file /etc/ld.so.conf like this:

Code:

/usr/lib64/seamonkey

Eric

Eric, I have the seamonkey-solibs package installed, but chrome still does not see the nss libs. If I install the mozilla-nss package from SlackBuilds.org, chrome sees the nss libs just fine. Is this a chrome bug?