MX Linux Forum

Green451@mepis1:~$ /opt/google/chrome/google-chrome %U
[3976:4004:1002/140204: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.
Aborted

* * *
Here is link I found searching: http://git.chromium.org/gitweb/?p=chrom ... 486f87b42b

Somebody please check and correct me if i am wrong: Apparently there are some security updates in the newer version: 3.14.3 contains a number of important security fixes, and support for older systems is no longer desirable.


More info just found: http://www.esecurityplanet.com/browser- ... flaws.html

Related? I do not know for certain...

namida12 wrote:Green451@mepis1:~$ /opt/google/chrome/google-chrome %U
[3976:4004:1002/140204: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.
Aborted

* * *
Here is link I found searching: http://git.chromium.org/gitweb/?p=chrom ... 486f87b42b

Somebody please check and correct me if i am wrong: Apparently there are some security updates in the newer version: 3.14.3 contains a number of important security fixes, and support for older systems is no longer desirable.

The version of libnss3 in the Wheezy repos is currently the 3.14.3-1 version: http://packages.debian.org/wheezy/libnss3, actually "2:3.14.3-1" -- but I don't think it checks the "2:" part. The google-chrome-stable package wouldn't have been installable/upgradeable if that version wasn't in the repos.

I'm not sure why it's complaining about the libnss3 version, it looks correct to me.

kmathern wrote:

namida12 wrote:Green451@mepis1:~$ /opt/google/chrome/google-chrome %U
[3976:4004:1002/140204: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.
Aborted

* * *

The version of libnss3 in the Wheezy repos is currently the 3.14.3-1 version: http://packages.debian.org/wheezy/libnss3, actually "2:3.14.3-1" -- but I don't think it checks the "2:" part. The google-chrome-stable package wouldn't have been installable/upgradeable if that version wasn't in the repos.

I'm not sure why it's complaining about the libnss3 version, it looks correct to me.

Technically NSS 3.14.3 depends on NSPR 4.9.5, but Debian stable still ships 4.9.2 on stable, so this is the lower bound. I looked for libnspr in synaptic, libnspr4 2:4.9.2-1 <---could this be the reason?

How would I use apt-get to try the upgrade NSPR 4.9.5

JR

From your first link http://git.chromium.org/gitweb/?p=chrom ... 486f87b42b

> Technically NSS 3.14.3 depends on NSPR 4.9.5, but Debian stable still
> ships 4.9.2 on stable, so this is the lower bound.

I wonder if maybe the Wheezy libnspr4 version is the problem? It's at version 4.9.2-1 {actually 2:4.9.2-1}.

Maybe Tim or Stevo could backport the sid/jessie version for the CR repo, it's currently at 4.10-1 {actually 2:4.10-1}

edit: oops you already posted the same

namida12 wrote:How would I use apt-get to try the upgrade NSPR 4.9.5

The sid/jessie versions aren't installable on M12/Wheezy because of a "libc6 (>= 2.15)" dependency, M12/Wheezy uses libc6 2.13. It needs to be backported to be installable. Put in a request for it to be added to the M12 CRs.

kmathern wrote:From your first link http://git.chromium.org/gitweb/?p=chrom ... 486f87b42b

> Technically NSS 3.14.3 depends on NSPR 4.9.5, but Debian stable still
> ships 4.9.2 on stable, so this is the lower bound.

I wonder if maybe the Wheezy libnspr4 version is the problem? It's at version 4.9.2-1 {actually 2:4.9.2-1}.

Maybe Tim or Stevo could backport the sid/jessie version for the CR repo, it's currently at 4.10-1 {actually 2:4.10-1}

I will wait for fix as I can not believe i am the only Google browser Mepis user that would like the latest security updates in their web browser.

That is part of testing a beta, I hope...

JR

namida12 wrote:I will wait for fix as Ii can not believe i am the only Google browser mepis user that would like the latest security updates in their web browser.

That is part of testing a beta, I hope...

JR

It's kind of disturbing that Google pushed thru an update that breaks Chrome on a stock Debian Stable/Wheezy install, when it's still a fairly new release.

Back in April their update to Chrome 26 broke it on stock Squeeze installs, but Squeeze was more than 2 years old at that time, it's only been 5 months since Wheezy's release.

kmathern wrote:It's kind of disturbing that Google pushed thru an update that breaks Chrome on a stock Debian Stable/Wheezy install, when it's still a fairly new release.

Being treated like the bastard stepchild does get kinda old, doesn't it?

kmathern wrote:

namida12 wrote:I will wait for fix as Ii can not believe i am the only Google browser mepis user that would like the latest security updates in their web browser.

That is part of testing a beta, I hope...

JR

It's kind of disturbing that Google pushed thru an update that breaks Chrome on a stock Debian Stable/Wheezy install, when it's still a fairly new release.

Back in April their update to Chrome 26 broke it on stock Squeeze installs, but Squeeze was more than 2 years old at that time, it's only been 5 months since Wheezy's release.

* *
kmathern & uncle mark,

This is the first time I have ever had a broken Google Chrome web browser in Mepis. I was always loading Chromium instead of directly from Google several years ago, but I started downloading directly about three years ago when I began using AntiX more often.

But seeing Google change versions with a large number of security fixes, does not worry me, and seeing the notice of June Sat, 29 Jun 2013 Bug report, a 60 day old item that apparently did not mater to me until this Web browser update is not the end of the world.

I am certain this will be corrected in time, my concern is not having a Google web browser secure as designed...

I am certain this will be a system wide problem for Debian & Debian based distro users something not limited to the Mepis beta.

JR

Just got GC Version 30.0.1599.66 today and it runs fine in Kubuntu 13.04. As I recall I downloaded an earlier version and it just keeps upgrading when newer ones come out. None have been a problem. So it does not appear to be a widespread problem. I should not say that as I can only speak for my system.