37274 - profile manager isn't launching on a clean install.

Status: VERIFIED INVALID

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

Description

[Joseph Elwell]

winNT build 2000042608, the profile manager failed to launch when I launch 
mozilla with a clean (deleted mozregistry.dat, Users50 directory, 
mozversion.dat) install.

Comment 1

[Grace Bush]

cannot reproduce here. 
Do you have a Netscape 4.x profile (s)? Does Mozilla launch? 

Comment 2

[Joseph Elwell]

I do have a 4.x profile, but that profile isn't used. I get a profile created 
called "default" (not "Default User"), the bookmarks show that my IE bookmarks 
were imported. Mozilla does indeed launch, with this "default" user.

Comment 3

[Grace Bush]

My understanding is with 0 4.x and 0 6.0 profiles and launching with -installer 
option - a default profile called default will be created for launch.  This 
default profile will also be created if the automigration of a 4.x profile 
fails.
To see Profile Manager, run with -profilemanager option. 
Can you tell me what you mean by '4.x profile not used' - was it created by 4.x 
Profile Manager and therefore registered in nsreg.dat? Since deleted in 4.x 
Profile Manager? because mozilla will look at nsreg.dat for profiles to migrate.

Comment 4

[Cyril Bortolato]

I see the problem on Linux as well, build 2000-04-26-09. I did:
1) mv .netscape .turlututu
2) rm -r .mozilla
3) launch mozilla

Profile manager did not come up, and a default profile was created.

Changing OS to "All".

Comment 5

[selmer (gone)]

Bhuvan, I've been hearing this from different quarters.  Did we change
something?  I notice Ben's changed the UI again, maybe something got out of sync.

Comment 6

[racham]

I pulled the latest build (2000-04-26-11-M16) and cleaned machine (no 
mozregistry, no mozver.dat, no Users50 and no nsreg.dat)and installed it. A 
default profile gets created and I am launched into the browser window. It works 
fine and is the expected behavior. This is on my windows box. 

I did the same thing on Linux with latest builds (both mozilla and netscape). I 
couldn't reproduce the behavior explained above. The browser came up in all the 
cases using the profile default.

I guess the builds lately have been little unstable and what we are experiencing 
could be corrupted bits or some other module problem exposed by profile manager 
in specific builds.

Let us check the behavior on the builds that will be posted tomorrow.

Comment 7

[Grace Bush]

Bhuvan,

Using [e-mail]'s steps - actually removing 4.x profile, I can reproduce 
this. Launching mozilla with no options in this instance *should* bring up 
ProfileWizard.
I was assuming in earlier tests that launch was with -installer option, which 
would create default profile.
Will check on today's builds as you suggested 

Comment 8

[racham]

When U moved activation code to ns tree, there is small change that I brought in  
along with it. If we have zero 6.0 profiles, we used to see CreateProfileWizard 
in the past. That now is changed. We now create profile 'default' and proceed. 
We don't show createprofile wizard. For some one to create a profile of thier 
choice. One can always use profile manager for creating profiles with customized 
names.

Comment 9

[Grace Bush]

Then this is working as designed- or invalid?
Should we post functionality here - in release notes?

Comment 10

[racham]

We should post in the release notes......Grace, Can you talk to verah about 
this ?

Please use -ProfileWizard from the command line for CreateProfileWizard
or -ProfileManager to create new profile with the name of your choice.

Marking this bug invalid.

Comment 11

[racham]

Also small correction in the bug update I made at 2000-04-27 10:14.

Addressing Grace, I wrote.....

When U moved activation code to ns tree, there is .....

and it should be read as 

When I moved activation code to ns tree, there is .....

sorry grace !

Comment 12

[Grace Bush]

no problem, no one calls me U