Closed
Bug 13339
Opened 25 years ago
Closed 25 years ago
[PP]Errors when migrating 4.x profile - in prefs.js file
Categories
(Core Graveyard :: Profile: Migration, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M11
People
(Reporter: agracebush, Assigned: dbragg)
Details
Attachments
(1 file)
448 bytes,
text/html
|
Details |
Steps to reproduce: 1. Launch apprunner -installer 2. Migrate a 4.x profile 3. Or use a profile migrated (9/8 build) Expected result: Profile migrated Actual result: two errors pop up during migration, error in prefs.js file Profile is migrated- Will attach error displays. Prefs.js file is missing // before first two lines. # before line 1, nothing before line 2 Builds 1990908 on Win
Reporter | ||
Comment 1•25 years ago
|
||
Reporter | ||
Comment 2•25 years ago
|
||
Don, If you cannot see this attachment I will mail to you. It basically says it cannot read startup configuration file---missing ';' before statement. This is a generated file! Do not edit and 'error in preference file, will use default prefs'
This was weird. The error was on a line in the prefs.js file that I don't touch. Accepting the bug but I'm not really sure it's mine. The fix may be checked in today.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I removed mulitple calls to PREF_SavePrefFile. This had the effect of cleaning up the prefs.js file. I then ran a migrated profile and got no errors. Methinks is fixed.
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 5•25 years ago
|
||
build 19990914xx on Win32
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•