| 1 |
On Monday, 16 September 2019 14:03:37 BST Mick wrote: |
| 2 |
> On Monday, 16 September 2019 08:47:33 BST Peter Humphrey wrote: |
| 3 |
|
| 4 |
> > 1568619006132 Marionette FATAL <window id="main-window" |
| 5 |
> > ^ |
| 6 |
> > JavaScript error: resource://gre/modules/AutoCompletePopup.jsm, line 113: |
| 7 |
> > NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057 |
| 8 |
> > (NS_ERROR_ILLEGAL_VALUE) [nsIObserverService.removeObserver] |
| 9 |
> > |
| 10 |
> > Pro tem I've negated all the system-* flags in package.use. |
| 11 |
> |
| 12 |
> I've noticed a similar failure to launch on one system here. It works when |
| 13 |
> launched with --safe-mode, so I assumed some of the many addons on this |
| 14 |
> system are causing the failure. Other systems do not have such problems. |
| 15 |
|
| 16 |
Actually, on two systems FF 68 has been a disaster: |
| 17 |
|
| 18 |
As reported by Peter, it crashes when launched. |
| 19 |
|
| 20 |
I have found three approaches to allow it to launch. |
| 21 |
|
| 22 |
1. Start it with --safe-mode. A pain, because I have to re-enable the Menu to |
| 23 |
become visible as well as the Bookmards Toolbar. By definition all addons and |
| 24 |
extensions are disabled. |
| 25 |
|
| 26 |
2. Remove all my tweaked preference settings: |
| 27 |
|
| 28 |
I deleted all of my customised preferences by moving ~.mozilla/firefox/ |
| 29 |
XXXXXXXX.default/prefs.js |
| 30 |
|
| 31 |
Then restarted it. It launched with its new start up page and what not. |
| 32 |
Everything worked. I did NOT change any settings what-so-ever. I closed it |
| 33 |
and relaunched it. The window now has no window title bar at the top. It |
| 34 |
also shows no bookmarks. Menus are empty. What the ... ?! |
| 35 |
|
| 36 |
3. Create a new blank profile. This works fine, until/unless I try to tweak |
| 37 |
telemetry settings. |
| 38 |
|
| 39 |
|
| 40 |
It seems 1. above works, but it's a pain. Approach 2. works too, but only |
| 41 |
once. Approach 3. appears to work so far. I disabled the Sync function too |
| 42 |
and it still launches. This change in behaviour of a browser which worked |
| 43 |
without any major hickups here for many years is bloody annoying. O_O |
| 44 |
|
| 45 |
I don't mind recompiling it if this is what must happen, is there any |
| 46 |
particular system-* USE flag which I should disable? BTW, in previous |
| 47 |
versions I have these FF USE flags set in a corresponding package.use file: |
| 48 |
|
| 49 |
system-harfbuzz system-icu system-jpeg system-libevent system-libvpx system- |
| 50 |
sqlite -wifi |
| 51 |
|
| 52 |
-- |
| 53 |
Regards, |
| 54 |
|
| 55 |
Mick |
Archives