google chrome 30
Slackware64-14, latest version of google-chrome (30.0.1599.66), installed using the slackbuild that came with the DVD. I'm getting this:
12167:12193:1001/141258:FATAL:nss_util.cc(396)] NSS_VersionCheck("3.14.3") failed. NSS >= 3.14.3 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.
NSS (mozilla-nss) is 3.15. Any ideas how to either fix this or where I can find the last version of the 29.xx tree? (Stupidly, I didn't save it when I upgraded the package.)\
ETA: I may just switch back to firefox out of pure spite.
Gotcha, thanks. I must've misread *.13 for *.15.
Well maybe it isn't solved.
I just grabbed mozilla-nss from /current, compiled it, and upgraded it. Same error. I'm wondering if the issue isn't with them?
ETA: double-checked that I compiled the right one (x86-64).
I have a -current machine and building Google Chrome is not a problem here
After read your post I updated my google-chrome using ruario's script (latest-chrome.sh),I use Slackware64-14.0 and no problems at all. The script can be found at http://www.panix.com/~ruari/latest-chrome . Good luck!
From the start this post made no sense to me. The error complains about an older NSS version but as Alien Bob pointed out in the first reply, Slackware 14 already has a version of NSS that is more recent than what is required. Sure enough Chrome stable works just fine for me (indeed I can even run Google Chrome 30.0.1599.66 beta and Google Chrome 31.0.1650.4 dev without issue).
From my own system:
Also do you have a full install? I just noticed whilst looking at my own ldd output that Chrome is using the /usr/lib64/seamonkey/libnss3.so, which is from seamonkey-solibs-2.20-x86_64-2_slack14.0, rather than the mozilla-nss-3.13.5-x86_64-3.
P.S. It is not a problem that nacl_helper_bootstrap and nacl_irt_x86_64.nexe state "not a dynamic executable" in my above output because they are statically linked binaries.
As side note since Alien Bob is reading this, you might want to mention to Pat that google-chrome-pam-solibs is no longer needed by Chrome, so could potentially be removed from /extra on -current. This has been the case since at least February.
Additionally this part of google-chrome.SlackBuild is now redundant:
Yes, full install. (From a few days ago, even.) Yes, 64 bit.
Here's what LDD shows:
% /opt/google/chrome ldd chrome hildegard@guibert
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f53c0736000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f53c052d000)
libXss.so.1 => /usr/lib64/libXss.so.1 (0x00007f53c0329000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f53c0118000)
librt.so.1 => /lib64/librt.so.1 (0x00007f53bff10000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f53bfd0b000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f53bfabe000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f53bf7a0000)
libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x00007f53bf16e000)
libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x00007f53beebc000)
libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007f53bec9a000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007f53bea8d000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f53be86e000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007f53be5c0000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007f53be374000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f53be0e8000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f53bdeb2000)
libnss3.so => /usr/lib64/seamonkey/libnss3.so (0x00007f53bdbac000)
libnssutil3.so => /usr/lib64/seamonkey/libnssutil3.so (0x00007f53bd98a000)
libsmime3.so => /usr/lib64/seamonkey/libsmime3.so (0x00007f53bd763000)
libplc4.so => /usr/lib64/seamonkey/libplc4.so (0x00007f53bd55e000)
libnspr4.so => /usr/lib64/seamonkey/libnspr4.so (0x00007f53bd320000)
libgconf-2.so.4 => /usr/lib64/libgconf-2.so.4 (0x00007f53bd0fa000)
libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007f53bcef7000)
libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007f53bcc08000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f53bca06000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f53bc7ff000)
libcups.so.2 => /usr/lib64/libcups.so.2 (0x00007f53bc5b4000)
libgcrypt.so.11 => /lib64/libgcrypt.so.11 (0x00007f53bc337000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f53bc11a000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f53bbef1000)
libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007f53bbcad000)
libudev.so.0 => /lib64/libudev.so.0 (0x00007f53bba9f000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f53bb79e000)
libm.so.6 => /lib64/libm.so.6 (0x00007f53bb4a3000)
libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f53bb28d000)
libc.so.6 => /lib64/libc.so.6 (0x00007f53baecd000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f53bacaf000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f53baaab000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f53ba8a6000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007f53ba6a4000)
libffi.so.6 => /usr/lib64/libffi.so.6 (0x00007f53ba49c000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f53ba29a000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f53ba08b000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f53b9e83000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f53b9c79000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f53b99f3000)
libpng14.so.14 => /usr/lib64/libpng14.so.14 (0x00007f53b97ce000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f53b9482000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f53b9267000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007f53b903b000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f53b8e38000)
libz.so.1 => /usr/lib64/libz.so.1 (0x00007f53b8c22000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f53b8a12000)
libplds4.so => /usr/lib64/seamonkey/libplds4.so (0x00007f53b880e000)
libdbus-glib-1.so.2 => /usr/lib64/libdbus-glib-1.so.2 (0x00007f53b85e6000)
libssl.so.1 => /lib64/libssl.so.1 (0x00007f53b837e000)
libcrypto.so.1 => /lib64/libcrypto.so.1 (0x00007f53b7fa2000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f53b7d6a000)
libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00007f53b7b67000)
Hang on. It's getting libnss3.so from /usr/lib64/seamonkey. Is that right? Shouldn't it be getting it from mozilla-nss, instead?
Granted, I've had no coffee yet, but if I upgrade seamonkey it should theoretically work?
Still seems like a problem that it's loading some libraries from another browser...
Slightly caffeinated. Upgraded seamonkey, and google chrome works again. Seems like really poor behavior on chrome's part, though, to prefer seamonkey's libraries over mozilla-nss.
The source of your issue however was that you didn't keep all of you Slackware packages up to date. Why are you selectively applying the security updates?
Also it is apparently not that weird, given that Chrome doesn't appear to work with just the mozilla-nss-3.13.5-x86_64-3 package. If you remove seamonkey-solibs Chrome will not start, you will get the "NSS >= 3.14.3" error. I just tried it.
|All times are GMT -5. The time now is 04:50 AM.|