Closed
Bug 13573
Opened 25 years ago
Closed 25 years ago
JS Error at startup reading prefs file on migrated profile
Categories
(Core :: Preferences: Backend, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: paulmac, Assigned: neeti)
References
()
Details
I just tried migrating my 4.x profile over and I am getting a start-up error
that seems to prevent my prefs.js file from being read. The error says "An error
occurred reading the startup configuration file. Please contact your
administrator. missing ; before statement. This is a generated file! Do not
edit.
and after pressing OK
"Error in prefs.js file. Default preferences will be used."
I placed my prefs.js file, which works fine in 4.x, at
http://slip/projects/dogbert/test/install/
Paul,
How did you migrate the profile? The comments are being removed during profile
migration. Your prefs.js file after migration has the following lines
# Mozilla User5 Preferences
This is a generated file! Do not edit
But it should be
# Mozilla User5 Preferences
//This is a generated file! Do not edit.
We have the comments in the 4.x prefs file also.
Neeti
Reporter | ||
Comment 2•25 years ago
|
||
I used the apprunner -installer command and then selected the profile and
clicked on Migrate.
Paul, could you try the migration again, because when I do it, I get the
following lines in my prefs.js file
# Mozilla User5 Preferences
//This is a generated file! Do not edit.
I do not get start-up error.
Thanks,
Neeti
Reporter | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•25 years ago
|
||
I deleted all my profiles except one, because I heard there was problems with
migrating multiple profiles,and then migrated, and everything is now OK. Thanks.
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Moving all libPref component bugs to new Preferences: Backend component.
libPref component will be deleted.
Component: libPref → Preferences: Backend
You need to log in
before you can comment on or make changes to this bug.
Description
•