Re: Chromium fatally broken

2016-11-08 Thread Curt
On 2016-11-08, Cindy-Sue Causey  wrote:
>
> Hi, Curt.. I can't give you insight on the error because(y) mine's
> working ok. Sounded at least slightly familiar so I quick searched my
> inbox. Got 2 emails that I then searched the Net and found you
> these...
>
> https://www.debian.org/security/2016/dsa-3688

Hello. Apparently chromium is no longer supported in Wheezy for the near
and distant future. And that, as they say in French, explains that.

Thank you.

-- 
“It is enough that the arrows fit exactly in the wounds that they have made.”
Franz Kafka



Re: Chromium fatally broken

2016-11-08 Thread Curt
On 2016-11-08, david...@freevolt.org  wrote:
>
>> 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.
>> [...]
>

Thank you. I didn't think of exploring that angle of my problem.

-- 
“It is enough that the arrows fit exactly in the wounds that they have made.”
Franz Kafka



Re: Chromium fatally broken

2016-11-08 Thread Cindy-Sue Causey
On 11/8/16, 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?


Hi, Curt.. I can't give you insight on the error because(y) mine's
working ok. Sounded at least slightly familiar so I quick searched my
inbox. Got 2 emails that I then searched the Net and found you
these...

https://www.debian.org/security/2016/dsa-3688

"Debian Security Advisory [k/t Debian-Security list]

DSA-3688-1 nss -- security update
Date Reported: 05 Oct 2016
Affected Packages: nss
Vulnerable: Yes"

https://lists.debian.org/debian-user/2016/11/msg00136.html

It's recent Debian-User, and Wheezy gets a mention..

Hope that helps at least a little.. :)

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* You gotta find your #crochet-t-t-t.! *