Ubuntu
firefox-3.0 package

Can't lock preferences in Firefox 3.0 Beta 5

Bug #221265 reported by Nick Ellery
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mozilla Firefox
New
Unknown
firefox-3.0 (Ubuntu)
Triaged
Low
Unassigned

Bug Description

I try to lock preferences in Firefox 3.0 beta 5 on ubuntu 8.04 RC but it doesn't work.
I've tried to update the /etc/firefox-3.0/pref/firefox.js:
lockPref("network.proxy.type", 1);

but it doesn't work.
If I use "pref" instead of "lockPref" the setting is taken into account.
It worked with Firefox 2 (by modifying the /usr/lib/firefox/firefox.cfg file)

See original description
Revision history for this message
In , Mike Connor (mconnor) wrote :

This is a question of UI, but the preferences don't really change, do they?

Revision history for this message
In , Modesser (modesser) wrote :

(In reply to comment #1)
> This is a question of UI, but the preferences don't really change, do they?
>

Clicking twice on "Use blank page" sets the home page to "about:blank". The setting is not saved for the current browsing session, but it _is_ saved in prefs.js. Therefore, if the lock on browser.startup.homepage is released, the loaded URL on startup will be about:blank.

Revision history for this message
In , Modesser (modesser) wrote :

Created attachment 217553
How to be sure that the action will not change the preference.

This code is to be added at the beginning of methods setHomePageToCurrentPage(), setHomePageToBookmark(), setHomePageToDefaultPage() and setHomePageToBlankPage() in file chrome://browser/content/preferences/general.js

Revision history for this message
In , Modesser (modesser) wrote :

Created attachment 217554
How to be sure that the action will not change the preference.

This code is to be added at the beginning of methods setHomePageToCurrentPage(), setHomePageToBookmark(), setHomePageToDefaultPage() and setHomePageToBlankPage() in file chrome://browser/content/preferences/general.js

Revision history for this message
Nick Ellery (nick.ellery) wrote :

I try to lock preferences in Firefox 3.0 beta 5 on ubuntu 8.04 RC but it doesn't work.
I've tried to update the /etc/firefox-3.0/pref/firefox.js:
lockPref("network.proxy.type", 1);

but it doesn't work.
If I use "pref" instead of "lockPref" the setting is taken into account.
It worked with Firefox 2 (by modifying the /usr/lib/firefox/firefox.cfg file)

Revision history for this message
In , Fabio Correa (facorread) wrote :

This is also an issue in
Mozilla/5.0 (X11; U; Linux x86_64; es-CO; rv:1.9.0.4) Gecko/2008121822 Gentoo Firefox/3.0.4

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in firefox-3-0.

You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in firefox-3.0:
status: New → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in firefox-3.0:
status: Incomplete → Invalid
Changed in firefox:
status: New → Invalid
Revision history for this message
Yves Glodt (yglodt) wrote :

I need to use Hardy for at least 2 more years.

Just want to say that I am still unable to lock down certain preferences in Ubuntu hardy in an way that will not be overwritten by a package upgrade.

I added the following line to /etc/firefox-3.0/pref/firefox.js

pref("general.config.filename", "local.cfg");

The file "local.cfg" is then loaded from /usr/lib/firefox-3.0.5/ ... which is of course lost when the package gets upgraded.

Is there a way in ubuntu to provide a local configfile to force preferences without it being overwritten by package upgrades?

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thanks for your answer. Since you are still heaving the issues you should report this at https://bugzilla.mozilla.org/ where the developer of the software can read it. Thanks in advance.

Changed in firefox-3.0:
status: Invalid → New
Changed in firefox:
status: Invalid → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Yves, that's a different issue and you need to open a new report about that. This looks similar to bug https://bugzilla.mozilla.org/show_bug.cgi?id=330590 ; linking to the report, Nick may you please test the same with latest firefox package on jaunty? Thanks in advance.

Changed in firefox-3.0 (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Changed in firefox:
importance: Undecided → Unknown
status: New → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in firefox:
importance: Unknown → Medium
Revision history for this message
In , Mozilla-kaply (mozilla-kaply) wrote :

There are three additional preferences that when set and locked disable those buttons.

It's not tied to the locking of the homepage:

http://mxr.mozilla.org/mozilla-central/source/browser/components/preferences/main.xul#76 pref.browser.homepage.disable_button.current_page
pref.browser.homepage.disable_button.bookmark_page
pref.browser.homepage.disable_button.restore_default

If you set these three preferences to true and then lock the preferences, they will be disabled.

If you want to prevent the changes of the proxy preferences, you need to lock

network.proxy.type as well.

I'm going to mark this bug as INVALID.

Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: New → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in firefox:
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in firefox:
importance: Medium → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.