google chrome 30

ruario · 10-02-2013, 01:38 PM

Quote:

Originally Posted by garpu

parse error near 'do'.

Sorry, I assumed you use bash. This was probably a poor assumption.

ruario · 10-02-2013, 01:47 PM

Traditionally NSS libs have always been provided by seamonkey-solibs on Slackware. I must admit I am unsure why, once mozilla-nss was included, the seamonkey-solibs package remained (I'm making the assumption that mozilla-nss worked of course).

EDIT 1: I just bumped this thread about this issue.

EDIT 2: Read that thread, it all makes sense.

garpu · 10-02-2013, 11:10 PM

Ooooh. Yeah, that does make sense.

ruario · 10-03-2013, 02:07 PM

From the Slackware 14 changelog:

Code:

Thu Oct  3 02:57:44 UTC 2013
patches/packages/mozilla-nss-3.15.2-i486-1_slack14.0.txz:  Upgraded.
  Upgraded to nss-3.15.2 and nspr-4.10.1.
  This should help keep Google Chrome updates working for a while.
  Also, adding /lib and /usr/lib (or /lib64 and /usr/lib64) to the
  top of /etc/ld.so.conf will help Chrome use the correct libraries
  instead of the ones from Seamonkey.

Thanks Pat. I just tested and indeed it is possible to run Google Chrome (without seamonkey or seamonkey-solibs installed) again.

P.S. I also tried leaving seamonkey-solibs and tweaking /etc/ld.so.conf as per the suggestion, which (as expected) works just fine as well.

1337_powerslacker · 10-04-2013, 10:17 PM

Quote:

Originally Posted by ruario

From the Slackware 14 changelog:

Code:

Thu Oct  3 02:57:44 UTC 2013
patches/packages/mozilla-nss-3.15.2-i486-1_slack14.0.txz:  Upgraded.
  Upgraded to nss-3.15.2 and nspr-4.10.1.
  This should help keep Google Chrome updates working for a while.
  Also, adding /lib and /usr/lib (or /lib64 and /usr/lib64) to the
  top of /etc/ld.so.conf will help Chrome use the correct libraries
  instead of the ones from Seamonkey.

Thanks Pat. I just tested and indeed it is possible to run Google Chrome (without seamonkey or seamonkey-solibs installed) again.

P.S. I also tried leaving seamonkey-solibs and tweaking /etc/ld.so.conf as per the suggestion, which (as expected) works just fine as well.

Confirmed. I closed Chrome, made the additions suggested by Pat, removed the seamonkey and seamonkey-solibs packages, and re-launched Chrome. Works like a charm.

Regards,

Matt