Closed Bug 108706 Opened 24 years ago Closed 24 years ago

Preferences are not read or written when profile is loaded from commandline using "-P"

Categories

(Core Graveyard :: Profile: BackEnd, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 108383

People

(Reporter: cmanske, Assigned: ccarlen)

Details

I started seeing this in my debug build on 11/5/01. I'm not sure if it's a profile or prefs problem. Start Browser from commandline (or setup a Windows desktop icon) with a profile. e.g., I use "-P Debug" The console window correctly shows "Debug" as the profile it's using during startup. But the associated prefs.js file is not being read. To test: In Prefs | Appearance | Fonts: Change the default font to "Sans Serif" Exit prefs and the app. Restart using "-P" and profile name. The new font pref was not written to the correct prefs.js file. I don't see any errors in the console window about failing to write prefs, and can't find any other prefs.js that it might be writing to! Note that starting the app and selecting profile from the dialog works fine.
Maybe this is related to the conversion from using nsIPref to nsIPrefBranch? (see bug 106159)
Adding Brian Nesse, who knows about prefs.
The last checkin relating to the nsIPref -> nsIPrefBranch checkin was on 10/30. If this appeared yesterday, it's releated to something else. I noticed this morning that when I go into the font prefs panel, I never have a "default selection". It's just blank. If I set it, dismiss the dialog, and open it back up, it's blank again. I don't know if it was like this yesterday or not.
*** This bug has been marked as a duplicate of 108383 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Verified as a duplicate of 108383
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.