149243 - Profiles created in Profile/Conversion Manager not saved

Status: VERIFIED DUPLICATE of bug 133726

(Core Graveyard :: Profile: Migration, defect)

Description

[David Walton]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Mac_PowerPC)
BuildID:    2002052305

Launching mozilla after install brings up Confirm Migration dialog.  Clicking "Convert 
profile" does nothing (mozilla exits).  So, I tried clicking "Manage profiles...".  Here is 
what happens:


Reproducible: Always
Steps to Reproduce:
1.  Launch Mozilla.  "Confirm Migration" dialog appears.
2.  Clicking "Convert profile" causes Mozilla to exit (always), so try clicking "Manage 
profiles...."
3.  Profile Manager dialog appears.
4.  Click "Create profile."
5.  At information screen, click "Next" to start the process.
6.  Leave "Default user" name unchanged.  Click "Choose folder" to select a folder.  
(Have used various folders in various locations, including Preferences, root directory of 
startup disk, and folder called "Profiles" in Mozilla folder.)
7.  Click "Finish."
8.  Back at main Profile Manager screen, click "Start Mozilla."  Mozilla runs.
9.  Quit Mozilla.  Relaunch.  "Confirm migration" dialog appears again.  
10.  Click on "Manage profiles."  Default profile created in steps 4-7 doesn't appear in the 
list of available profiles.  So, go through steps 4-7 again.

Actual Results:  Profile created in profile manager doesn't show up in profile list; a fresh 
launch of mozilla requires creating a new profile each time.

Expected Results:  Created profile should be recognized by profile manager, allowing me 
to select it and launch mozilla.

- Although any profile created this way doesn't show up in the profile list, a quick glance 
shows that the appropriate folder ("Default user:sqd8cxp2.slt") and items in that folder 
(bookmarks, Cache, etc.) were in fact created.

- After starting up, a quick check of the JavaScript console always shows the following 
error message, repeated twice:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 
(NS_ERROR_FAILURE) [nsIProperties.get]"  nsresult: "0x80004005 
(NS_ERROR_FAILURE)"  location: "JS frame :: 
chrome://communicator/content/profile/profileSelection.js :: StartUp :: line 51"  data: no]

- Creating multiple profiles, renaming them, deleting them, clicking "Exit" in profile 
manager after creating profiles, giving mozilla lots of memory (44 MB) and generally 
mucking around doesn't appear to effect the problem.

- System configuration: MacOS 9.1, 128MB RAM/129 virtual; 6GB disk; Mozilla set to 
standard memory (also upped to 44 MB).  

I've seen bugs on not being able to create profiles, but they were all listed as resolved, 
and this one is decidedly not.  I strongly doubt that this is a system configuration issue; 
although I do have a few non-standard items, I've tested this bug with MacOS 9 base 
extensions and observed it just as consistently.

Comment 1

[Andrew Hagen]

You could try deleting registry.dat and starting over. The danger is that
reference to all your existing profiles would be gone, so don't do that unless
that's okay.

Comment 2

[Sergei Rebrik]

I have exactly the same problem on a different platform: Windows 2000 Pro, SP2.

I also noticed in the earlier versions: Mozilla 0.9.7 and Netscape 6.2.1. Hoped 
that it is fixed in 1.0 - no luck. 

Comment 3

[David]

I am also having this EXACT same problem with MOZILLA 1.0. And I am running 
windows XP.  Mozilla can't find profiles after it has been closed then 
reopened.

Why is a profile even reqired any more??? Windows 2k, XP, Linux and even MAC 
OSX have proper multi user interfaces now.. IT is getting less common for 
people to share a login/desktop.. Most of the OSes are geared for unique 
logins now.  Profiles should be optional not default.

Comment 4

[Brian Nesse (gone)]

Dupe of 133726... profile info not saved after migration.

*** This bug has been marked as a duplicate of 133726 ***

Comment 5

[K'Trina Medina]

Verified as a dupe of bug 133726