If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

mismatched initial and default profile names

RESOLVED EXPIRED

Status

SeaMonkey
Startup & Profiles
--
trivial
RESOLVED EXPIRED
14 years ago
8 years ago

People

(Reporter: Brant Gurganus, Assigned: jag (Peter Annema))

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030808 Mozilla Firebird/0.6.1+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030808 Mozilla Firebird/0.6.1+

The initial profile on a clean installation is named "default" while the default
profile when you create one is name "Default User".  These should match.

Reproducible: Always

Steps to Reproduce:
1. Install Mozilla, Firebird, or Thunderbird clean.
2. Note the profile name it created ("default").
3. Now start the profile manager.
4. Delete the profile and create a new one.
5. Note the profile name supplied ("Default User").
Actual Results:  
The two defaults are mismatched.

Expected Results:  
They should match.

"Default User" is at
http://lxr.mozilla.org/seamonkey/source/profile/resources/locale/en-US/newProfile1_2.dtd#8

"default" appears to come from
http://lxr.mozilla.org/seamonkey/source/profile/src/nsProfile.cpp#106
Product: Browser → Seamonkey

Comment 1

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 2

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.