Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Unable to modify browser.launcherProcess.enabled through autoconfig

  • 6 replies
  • 1 has this problem
  • 10 views
  • Last reply by tm1

tm1
tm1
more options

I have implemented autoconfig and my cfg file is working with other settings, but pref("browser.launcherProcess.enabled", false); will not change the setting - the value is still set to true. Is this configurable through autoconfig?

I have implemented autoconfig and my cfg file is working with other settings, but pref("browser.launcherProcess.enabled", false); will not change the setting - the value is still set to true. Is this configurable through autoconfig?

All Replies (6)

Dinushi Dhananjani
Dinushi Dhananjani
more options

Hi ... this link will be help to you https://support.mozilla.org/en-US/kb/connection-settings-firefox

tm1
tm1 Question owner
more options

Can you be more specific? I can't see what connection settings have to do with turning off browser.launcherProcess through autoconfig.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I'm on Linux, so can't test this.

Did you check the Browser Console for possible error messages?

I'm not sure how this pref would work in this case because Firefox is already started when the profile is loaded.

See also:

Its code cannot start nor rely on prefs, XPCOM, nsString, crash reporter, or other aspects of the Gecko runtime. Header-only code that does not depend on xul.dll (such as MFBT) is safe to use in the launcher process;

tm1
tm1 Question owner
more options

Can anyone help with a simple answer? I like to know if I as an IT admin for several non admin users can change the Firefox setting "browser.launcherProcess.enabled" which since Firefox 68 has been set to true. I thought that any config settings could be changed with autoconfig and a cfg file. The user can always open about:config and change the setting manually, but I like to automate this.

Wesley Branton
Wesley Branton
more options

You need to make sure to use lockPref instead of just pref. Using just pref will only set the value, but it can still be changed by the user. Using lockPref will set the value and prevent the user from changing the value.

It sounds like you probably want to use the following code instead:

lockPref("browser.launcherProcess.enabled", false);

Hope this helps.

tm1
tm1 Question owner
more options

Using lockPref("browser.launcherProcess.enabled", false); did change the value from true to false, thanks Wesley, but is there no better solution besides using lockPref? Because now the user is unable to change it back. Why is just using the pref function not able to change the value of browser.launcherProcess.enabled?