[Mozilla Enterprise] Failed to read the configuration file after recent update
James Pearson
james-p at moving-picture.com
Thu Dec 12 16:19:18 UTC 2019
ArtSciNet wrote:
>
> I'm not sure exactly when it started, or with which updated version of the Firefox Quantum ESR, because I have not had the time to sit down and troubleshoot the problem until now, but sometime in the last month or 2 we get the "Failed to read the configuration file" when launching Firefox. You click ok and Firefox launches and works fine. Our current version of ESR is 68.3.0, and I know we did not have this when deploying 60.7.1, so somewhere in between it broke.
>
> I have traced the problem to my custom configuration file where we try to set google as the default search by doing the following:
>
> // Set Google as default search
> Components.utils.import("resource://gre/modules/Services.jsm");
> var searchService = Services.search;
> var engine = searchService.getEngineByName("Google");
> searchService.currentEngine = engine;
>
>
> If I comment out the last 2 lines then the error does not occur. I have not been able to search any new method or syntax of doing this for the current ESR version, and have not seen any other mentions of this from anyone else reporting this problem in my searching. I suppose it's not the end of the world if we don't set Google as the default search when deploying systems, but it was sure nice having it that way.
>
>
> Any advise from anyone on where to look for a new way of configuring this?
Can't you do this via Policies ?
See:
https://github.com/mozilla/policy-templates/blob/f972ec60de7f8a03e9846b3d4840cc01a8f1a8ec/README.md#searchengines--default
James Pearson
More information about the Enterprise
mailing list