Re: "stable" Chrome may segfault i386 Debian stable - e.g. M
Posted: Wed Oct 15, 2014 11:23 am
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.)
Support for MX and antiX Linux distros
http://forum.mxlinux.org/
Ha, ha...you're right! No joy. Loaded libnss3 from the test repo and still no go.dolphin_oracle wrote: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 wrote: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!
huh...installed fine for me.richb wrote:Will not install libnss3 from Jessie due to dependency on libnss3-1d, and vice versa.dolphin_oracle wrote: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!
Code: Select all
ldd /opt/google/chrome/libwidevinecdm.soCode: 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)You lost me.Stevo wrote: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.so32-bit wants 2.15, too.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)
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)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.Adrian wrote: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.