Closed Bug 49945 Opened 24 years ago Closed 24 years ago

4.7 prefs.js file edited after using Seamonkey

Categories

(Core Graveyard :: Profile: Migration, defect, P3)

HP
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: esther, Assigned: dbragg)

Details

Using build 2000-08-21-08 on win98 the 4.7 prefs.js file is edited when using 
Seamonkey.  
Not sure if this is related to 49699 but it's really bad so logging a new one 
per comments in bug 49767.  
Using today's build 0822 on win98, my 4.7 prefs.js file is being 
edited when using seamonkey.  When I went back to 4.7 and launched my profile, I 
got an error stating the prefs.js file had and illegal character #mozilla.  
OK'ing the error recreates a default prefs.js file so you lose your previous 
settings.  When I compared the original prefs.js file with the edited one these 
two lines were entered at the top along with the #Mozilla User Preferences:
user_pref("browser.cache.directory:, "C:\\Program 
Files\\Netscape\\Users\\esther\\Cache");
user_pref("browser.history.last_page_visitied", 
"http://home.netscape.com/browsers/6/su_setup.html");

1.  Removed registry.dat and mozregistry.dat from system.
2. Install NSetup6.exe and chose a profile to migrate when the Profile Manager 
comes up.
3. Go to your mail account and get msgs and read one.
4. Close Seamonkey.
5. Launch Seamonkey again using the command line -installer (you need to do this 
to see the list of profiles).
6. Chose the same profile that was just migrated.  Cancel out of the Activation 
and close the browser, exiting the product.
7. Go to 4.7 application and launch the same profile

Result: you get an error message stating your prefs.js file has an illegal 
character...  OK the error.  At this point your previous 4.7 prefs.js file is 
overwritten as a default prefs.js file.

Expected:  My 4.7 profile to launch without errors or losing my setting.
Still need to check other platforms.
Esther, I need to isolate whether this is a migration problem or not.  Could you 
check your 4.7 prefs.js IMMEDIATELY after the migration completes?  I put 
specific code in to make sure this didn't happen.  I copy the prefs.js file to 
the system "TEMP" directory and read/write prefs to that file.  Then it is 
copied to the new profile directory.  At no time should the 4.7 version of the 
file be written to in the migration routine.
Status: NEW → ASSIGNED
I downloaded this morning's build and it doesn't happen anymore.  This only 
happened on yesterday's build.  Would you like me to try this again on 
yesterday's build to isolate the problem in case it comes back.
No thanks Esther.  I don't think it'll come back (insert scary music here).  
Marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
I ran the 8-22-08 build again (which is the build where this happened, not the
8-21 build) and the 4.7 prefs.js file is edited after closing Seamonkey the 2nd
time.   The first time it goes through the migration, launches and when I
closem, I checke the  4.7 prefs.js file through explorer and it was OK.  I then
launched Seamonkey again using the command line -installer, selected the same
profile and closed it.  As soon as it closed the 2nd time it edited the 4.7
prefs.js file.  As I mentioned before, this is not happening with today's build
08-23-06.  Hope this helps.  
This is apparently a symptom of bug 49699 and is fixed with today's build.
Verified as fixed
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.