Re: Chromium fatally broken
On Tue, 8 Nov 2016, Curt wrote:
Anyone seeing this behavior?
[8679:8702:1108/173355:ERROR:nss_util.cc(856)] After loading Root Certs, loaded==false: NSS error code: -8018
[8679:8679:1108/173355:ERROR:desktop_window_tree_host_x11.cc(1478)] Not implemented reached in void views::DesktopWindowTreeHostX11::MapWindow(ui::WindowShowState)
[5:5:1108/173355:ERROR:nss_util.cc(211)] Error initializing NSS without a persistent database: NSS error code: -8023
[5:5:1108/173355:FATAL:nss_util.cc(213)] nss_error=-8023, os_error=0
[7:7:1108/173356:ERROR:nss_util.cc(211)] Error initializing NSS without a persistent database: NSS error code: -8023
[7:7:1108/173356:FATAL:nss_util.cc(213)] nss_error=-8023, os_error=0
Or is it just a Wheezy idiosyncrasy and completely irrelevant to
modern day concerns?
Perusing the LTS pages on the debian wiki recently (hat-tip to Jochen
Spieker),...
https://wiki.debian.org/LTS
...I learned something new, and possibly relevant:
https://wiki.debian.org/LTS/Wheezy#Not_supported_packages
Not supported packages
There are a set of packages not supported by Wheezy LTS. To check
the support status for packages installed on the system, use the
debian-security-support package, or check the list at
https://anonscm.debian.org/cgit/collab-maint/debian-security-support.git/tree/security-support-ended.deb7
chromium-browser is listed, and there is a pointer to this
announcement:
https://lists.debian.org/debian-security-announce/2015/msg00031.html
Subject: [SECURITY] [DSA 3148-1] chromium-browser end of life
- -------------------------------------------------------------------------
Debian Security Advisory DSA-3148-1 security@debian.org
http://www.debian.org/security/ Michael Gilbert
January 31, 2015 http://www.debian.org/security/faq
- -------------------------------------------------------------------------
Package : chromium-browser
Security support for the chromium web browser is now discontinued
for the stable distribution (wheezy). Chromium upstream stopped
supporting wheezy's build environment (gcc 4.7, make, etc.), so
there is no longer any practical way to continue building security
updates.
[...]
Reply to: