Closed Bug 270597 Opened 20 years ago Closed 16 years ago

Mozilla can not create profile when mozilla already has a profile named "default user"

Categories

(SeaMonkey :: Startup & Profiles, defect)

1.7 Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: leon.sha, Unassigned)

Details

When you start up mozilla with mozilla -P.
Mozilla can not create profile when mozilla already has a profile named "default
user".If you click cancel and try again, it will ok. But if you keep clicking
create and cancel, the bug maybe appear again.
In profile/resources/content/createProfileWizard.js#131, checkCurrentInput
should not be executed in the first wizard page. But infact it will be triggered. 
I believe it is caused by https://bugzilla.mozilla.org/show_bug.cgi?id=265456.
But I wander why there is no problem on trunk.
-P is for using an existing profile, not creating a new one.
(In reply to comment #2)
> I believe it is caused by https://bugzilla.mozilla.org/show_bug.cgi?id=265456.
> But I wander why there is no problem on trunk.

What makes you think this is caused by bug 265456? That did land on the trunk
not too long ago...
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

On Firefox -P offers me to create, select or delete a profile.

I'm using Mozilla Nightlies, and got different profiles for testing bugs on
older nightlies or releases. I don´t use a 'Default User' profile, as that gets
used or recreated when a profile gets corrupt, if you don´t have or use it, it
doesn´t get recreated, but created  ;-) 

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041104
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.5) Gecko/20041119
started directly, as I have multiple profiles, ProfileManager came up.
Click 'Manage User Profiles' and get see the buttons for creating, selecting and
deleting a profile.

Clicking 'create' brings up a welcome message with three buttons:

Profile 'default User' doesn´t exist: 
'Back' inactive/grey, 'Next>' active/black, 'Cancel' active/black
Profile 'default User' exists: 
'Back' inactive/grey, 'Next>' inactive/grey, 'Cancel' active/black

'Next' will bring you the screen for name selection, and suggests 'Default User'.

So if 'Default User' exists, you can´t go on on Mozilla 1.7, but can go back,
and delete that profile.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041118
if 'Default User' exists, you get the default screen, with 'Default User'
suggested, but a red warning that this profile exists and can´t be created.
Changing the name in the textbox will create the profile you want.

So this bug doesn´t exist in Firefox nor Mozilla Trunk, it´s Mozilla 1.7.x only.
OS: Linux → All
(In reply to comment #4)
> (In reply to comment #2)
> > I believe it is caused by https://bugzilla.mozilla.org/show_bug.cgi?id=265456.
> > But I wander why there is no problem on trunk.
> 
> What makes you think this is caused by bug 265456? That did land on the trunk
> not too long ago...
Because I backout this patch it works OK.
So I guess this is reason.
Product: Browser → Seamonkey
"Mozilla can not create profile when mozilla already has a profile named "default
user"."
How do you mean this? As in "the Next button is disabled" (because i see that
problem with 1.7.5 release)?
(In reply to comment #7)
> "Mozilla can not create profile when mozilla already has a profile named "default
> user"."
> How do you mean this? As in "the Next button is disabled" (because i see that
> problem with 1.7.5 release)?

Leon: Can you please answer that ^^ :-)?

(In reply to comment #8)
> (In reply to comment #7)
> > "Mozilla can not create profile when mozilla already has a profile named
"default
> > user"."
> > How do you mean this? As in "the Next button is disabled" (because i see that
> > problem with 1.7.5 release)?
> 
> Leon: Can you please answer that ^^ :-)?
> 
> 

You can know the detail from comments #5.
But seems it is not a problem any more on mozilla1.7.5 release.
So if you can not reproduce this bug anymore, just close it.
(In reply to comment #9)
> You can know the detail from comments #5.
> But seems it is not a problem any more on mozilla1.7.5 release.
> So if you can not reproduce this bug anymore, just close it.

In 1.7.5 it IS a problem.
Flags: blocking1.7.6?
Not going to hold 1.7.6 for this edge case bug.
Flags: blocking1.7.6? → blocking1.7.6-
We have compared the behaviour of the Mozilla 1.7 and Mozilla 1.7.5. The reason
for this problem is "/profile/resources/content/createProfileWizard.xul, line 40".
Call to "checkCurrentInput(this.value)" routine. But this check is required.  In
the checkCurrentInput() by enforcing an additional check on the error we can
avoid this problem.     
Since there is no more development in mozilla 1.7. I'll close this bug.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.