X
Tap here to go to the mobile version of the site.

Support Forum

Unable to modify browser.launcherProcess.enabled through autoconfig

tm1
Posted

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?
Quote

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.79 Safari/537.36

More Information

Dinushi Dhananjani
  • Top 25 Contributor
5 solutions 216 answers
Hi ... this link will be help to you https://support.mozilla.org/en-US/kb/connection-settings-firefox
Was this helpful to you? 0
Quote

Helpful Reply

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

Can you be more specific? I can't see what connection settings have to do with turning off browser.launcherProcess through autoconfig.
Was this helpful to you? 2
Quote
cor-el
  • Top 10 Contributor
  • Moderator
17685 solutions 159997 answers

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;

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: *https://wiki.mozilla.org/Platform/Integration/InjectEject/Launcher_Process/ 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;
Was this helpful to you? 0
Quote

Question owner

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.

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.
Was this helpful to you?
Quote
Wesley Branton
  • Top 10 Contributor
693 solutions 5500 answers

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.

You need to make sure to use <code>lockPref</code> instead of just <code>pref</code>. Using just <code>pref</code> will only set the value, but it can still be changed by the user. Using <code>lockPref</code> will set the value and prevent the user from changing the value. It sounds like you probably want to use the following code instead: <code>lockPref("browser.launcherProcess.enabled", false);</code> Hope this helps.
Was this helpful to you?
Quote

Question owner

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?

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?
Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.