So I got “Windows has detected a problem and is shutting down”* and after the restart needed to follow Ellis Dee’s instruction in #17 again. I suppose this means I should stop clicking “No, Later” when Firefox begs to update?
(* The problem that forced shut-down, I think, was pushing Play on my KMPlayer window while Firefox had gone swap-happy. I used to do perverse stress tests on Unix and essentially never panicked the kernel, but Windo$e requires careful fondling.)
This worked for me as well. Isn’t Mozilla in the process of preparing a new mobile browser for release next year? I’m wondering if that explains the lack of attention given to the bug in Firefox for Android.
Good article by the CTO of Mozilla. As I said earlier, I never had a problem anyway on my desktop, but that prompted me to upgrade my Android version of Firefox on which I had disabled addon signature verification. Weird update process in my case because it had to update two separate times, but in the end, it worked. UBlock Origin is no longer despised as “not verified”. I’ve turned off “xpinstall.signature.required” and I am still not presented with fantastic investment opportunities or penis enlargement aids from the fine advertisers on the SDMB, so it’s all good.
FTR, when I said just above "I’ve turned off ‘xpinstall.signature.required’ " I obviously mean I’ve changed it from “false” back to its default value of “true”. Anyway, the point is that Android users should be able to upgrade via Google Play and fix this problem. Desktop users should have had the fix some time ago. I don’t mess with this shit on my phone, but my tablet is an Amazon HD 8 which isn’t even supposed to have Google Play, which I sideloaded, and the Firefox update worked perfectly.
Both the prosecution and the defense would like to ask the court to dismiss juror one. And jurors two and six just because they’ve been sitting nearby.