Closed Bug 25985 Opened 25 years ago Closed 25 years ago

Profile Manager doesn't display profiles after exit.

Categories

(SeaMonkey :: Startup & Profiles, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 24911

People

(Reporter: laurel, Assigned: bugs)

Details

Using 2000-01-31-11m14 commercial build on NT 4.0 The profile manager dialog is not displaying profile names, except when they have just been created within that profile manager session. Once you exit the profile manager and start the Profile Manager again, the list is gone. Steps to reproduce: 1. Delete mozregistry.dat and any User50 files. 2. Launch mozilla -ProfileManager. Click new profile button, give the profile a name, confirm Finish. New profile name is displayed in Profile Manager dialog. 3. Click Exit to exit profile manager dialog. 4. Launch mozilla -ProfileManager again and again create a new profile with a different name than the one created in step 2. Confirm Finish. Both profile names are listed in Profile Manager dialog. 5. Exit and relaunch mozilla -ProfileManager. Actual result: profile manager dialog has a blank list. Expected result: profile manager dialog should have two entries. Note1: This same thing happens if you launch mozilla the first time through -installer, -mail or just mozilla(browser) and let a default profile be created. Note2: Launching mozilla -mail will pick up the profile list, whereas -ProfileManager does not. Summary: The profile manager is like a box of chocolates -- you never know what you're gonna get.
Summary: ProProfile Manager doesn't display profiles after exit. → Profile Manager doesn't display profiles after exit.
Setting platform to All. Happens linux rh6.0, NT 4.0 and mac OS 8.5.1
OS: Linux → All
Hardware: PC → All
This is basically Bug number 24911, which already has a discussion surrouding it.. *** This bug has been marked as a duplicate of 24911 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.