"stable" Chrome may segfault i386 Debian stable - e.g. MX14

[joany]

Thanks, Dolphin. I'll unpin Chrome and try installing and running it later today. (But I'm keeping Adrian's .deb file handy just in case.)

[Paul..]

Just unpinned google-chrome-stable and upgraded to 38.0.2125.104-1. Looks good. No Seg Fault...Doesn't handle Netflix, though...probably need to do something to libnss...

[dolphin_oracle]

you need at least the libnss3 from Jessie. Also, steveo says the drm library may not be compiled right for wheezy as well. netflix-desktop refuses to die!

[Paul..]

you need at least the libnss3 from Jessie. Also, steveo says the drm library may not be compiled right for wheezy as well. netflix-desktop refuses to die!

Ha, ha...you're right! No joy. Loaded libnss3 from the test repo and still no go.

[richb]

you need at least the libnss3 from Jessie. Also, steveo says the drm library may not be compiled right for wheezy as well. netflix-desktop refuses to die!

Will not install libnss3 from Jessie due to dependency on libnss3-1d, and vice versa.

[dolphin_oracle]

you need at least the libnss3 from Jessie. Also, steveo says the drm library may not be compiled right for wheezy as well. netflix-desktop refuses to die!

Will not install libnss3 from Jessie due to dependency on libnss3-1d, and vice versa.

huh...installed fine for me.

[Stevo]

The backported libnss3 is in the test MEPIS 12 CR. You can check the Widevine library yourself, however, currently it results in:

Code: Select all

ldd /opt/google/chrome/libwidevinecdm.so

Code: Select all

/opt/google/chrome/libwidevinecdm.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/google/chrome/libwidevinecdm.so)
/opt/google/chrome/libwidevinecdm.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/google/chrome/libwidevinecdm.so)

32-bit wants 2.15, too.

[Adrian]

That's the problem in my view with Debian Stable, it's too stable (read "stale") and virtually nobody targets it, not even Google. It might work well for servers and I can imagine it avoids many headaches that updating could potentially bring, but for desktop it's really not the best fit.

[richb]

The backported libnss3 is in the test MEPIS 12 CR. You can check the Widevine library yourself, however, currently it results in:

Code: Select all

ldd /opt/google/chrome/libwidevinecdm.so

Code: Select all

/opt/google/chrome/libwidevinecdm.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/google/chrome/libwidevinecdm.so)
/opt/google/chrome/libwidevinecdm.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/google/chrome/libwidevinecdm.so)

32-bit wants 2.15, too.

You lost me.

Code: Select all

richard@mx1:~
$ ldd /opt/google/chrome/libwidevinecdm.so
/opt/google/chrome/libwidevinecdm.so: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/google/chrome/libwidevinecdm.so)
	linux-gate.so.1 =>  (0xb76e6000)
	libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb70c2000)
	libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb709c000)
	libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb707e000)
	libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb7065000)
	libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb6f17000)
	/lib/ld-linux.so.2 (0xb76e7000)

Just saw your post in another thread re libc6. Explains the problem. Unfortunately we have two similar threads running.

[uncle mark]

That's the problem in my view with Debian Stable, it's too stable (read "stale") and virtually nobody targets it, not even Google. It might work well for servers and I can imagine it avoids many headaches that updating could potentially bring, but for desktop it's really not the best fit.

And that's always been the case, hasn't it? The tension between stability and new & shiny has been in evidence ever since I got involved with Debian based distros. Numerous attempts to straddle that divide have been attempted, with differing levels of success. For a desktop, a "stable testing" has always been the goal, it seems.

What has set MEPIS apart in the past and now with MX has been the work of the Community Packagers, who have been able to provide many/most of the latest & greatest packages while still maintaining the Debian stable base. But there's only so much they can do, and the older Debian stable gets, the harder that job becomes.

Of course, once Jessie goes stable, it will be much better... for a while. So it goes.