Closed Bug 1106951 Opened 11 years ago Closed 11 years ago

locking of preferences no longer possible

Categories

(Firefox :: Untriaged, defect)

34 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mozilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:34.0) Gecko/20100101 Firefox/34.0 Build ID: 20141125180439 Steps to reproduce: Updating from 33.1 to 34.0 (MacOS 10.10.1) broke preference-locking for me. My defaults/pref/local-settings.js was always stored under ../Firefox.app/Contents/MacOS/ but looking at http://kb.mozillazine.org/Locking_preferences suggests to store this file in Firefox.app/defaults/pref/local-settings.js. So here's what I did: * Downloaded & installed a fresh copy of "Firefox 34.0.5.dmg" * Install local-settings.js as per KB:Locking_preferences $ cat /Applications/Firefox.app/defaults/pref/local-settings.js // Do not obscure the content with ROT-13 pref("general.config.obscure_value", 0); pref("general.config.filename", "mozilla.cfg"); * Create mozilla.cfg $ cat /Applications/Firefox.app/mozilla.cfg lockPref("network.proxy.type", 0); * Start Firefox with a pristine (!) profile: $ /Applications/Firefox.app/Contents/MacOS/firefox -no-remote -ProfileManager Actual results: Go to "about:config" => and "network.proxy.type" was set to "5", the default value. Expected results: "network.proxy.type" should have been set to "0", as specified in mozilla.cfg. This was working perfectly up to 33.1, where I had defaults/pref/local-settings.js stored in Firefox.app/Contents/MacOS - so I tried the same for v34.0.5: -------------------- $ cat /Applications/Firefox.app/Contents/MacOS/defaults/pref/local-settings.js // Do not obscure the content with ROT-13 pref("general.config.obscure_value", 0); pref("general.config.filename", "mozilla.cfg"); $ cat /Applications/Firefox.app/Contents/MacOS/mozilla.cfg lockPref("network.proxy.type", 0); -------------------- Start Firefox with a pristine (!) profile: $ /Applications/Firefox.app/Contents/MacOS/firefox -no-remote -ProfileManager network.proxy.type is still "5", the default value :-\
Going back to 33.1.1 fixes this issue for me (and fixes another issue with the password store, for which I may have to file another report).
Raising the prio somewhat, as this is kinda major: I'd like to update Firefox because of MFSA-2014-90 but I can't as profiles are not working with Firefox 34.x. I also noticed that the whole Contents/MacOS/defaults/ directory does not even exist in Firefox 34.x - yet the release notes do not mention that. Help, please?
Severity: normal → major
Hrmpf, shortly ater posting the above I found it: the Contents/MacOS/defaults/ directory moved to Contents/Resources/defaults/ - sigh. This would make a nice entry in the changelog :-\
Severity: major → normal
(In reply to Christian Kujau from comment #3) > Hrmpf, shortly ater posting the above I found it: the > Contents/MacOS/defaults/ directory moved to Contents/Resources/defaults/ - > sigh. This would make a nice entry in the changelog :-\ This was (indirectly) referred to in the release notes for Firefox 34[1]: "Firefox signed by Apple OS X version 2 signature" The changes were (as you may have guessed) necessary to sign Firefox with Apple's v2 signatures. This happened in bug 1047584 and dependents. [1] https://www.mozilla.org/en-US/firefox/34.0/releasenotes/ Sounds like this is WFM now, so closing it. Please reopen if this is really broken. :-)
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.