Closed Bug 282741 Opened 20 years ago Closed 20 years ago

After I loaded SlipStream Web Accelerator, Mozilla created an entire new user & I "lost" all of my passwords

Categories

(SeaMonkey :: Passwords & Permissions, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: dloomis.nh.ultranet, Assigned: dveditz)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616

   I loaded Slipstream Web Accelerator and when I opened Mozilla, it opened up
as a brand new user.  I have found my various saved messages and coppied that
info into my new profile, but I need to know the name of the password manager
file in my old profile so I can copy it over too.

Reproducible: Always

Steps to Reproduce:
1. Set up a new profile in Mozilla
2. Password Manager, Bookmarks, and EMail messages don't appear in new profile.
3.

Actual Results:  
Password Manager file, Bookmark File, and EMail files aren't brought over into
the new profile.  I can find the old profile and copy the old Bookmark File, and
EMail file into the new profile but I don't know what Mozilla calls the Paswood
Manager file(s) so I can's copy this file properly.

Expected Results:  
   There is no problem with Mozilla, I merely need to know the name Password
Manager gives to the file of passwords, as well as the area in which it is
saved, so I can copy it over to the appropriate location in my new profile.
In Mozilla password files are <random>.s (and form-fill is <random>.w). If you
had encrypted your passwords you must also copy over cert8.db, key3.db and
secmod.db, which you'll also want to do if you have any stored certificates.

The new profile likely has a different <random> part. change the old name to the
new name, or else edit your prefs to change the pref to match the old name.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.