Closed Bug 7128 Opened 26 years ago Closed 26 years ago

Creating profile named "Default" ineffective

Categories

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

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 6592

People

(Reporter: jgmyers, Assigned: racham)

Details

Installed fresh build, deleted mozregistry.dat. Started apprunner, got the profile wizard. Created a profile, naming it "Default". Apprunner exited. Started apprunner again, got the profile wizard again.
Status: NEW → ASSIGNED
Target Milestone: M7
We are creating a profile named 'default' by default which we will get rid of this behavior pretty soon and create a single, real profile. Also, the registry seems to be operating in a case insensitive mode. In your case, it should have ideally created a profile named 'Default'.
Bug# 7132 is partially responsible for this behavior. Profile 'Default' should be treated differently from the default profile 'default'. However, this whole default behavior will be fixed soon.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
case insensitivity of the libreg routines is causing this problem. Rename suffers from the same issue. So, I'm marking this duplicate of bug #6592 (rename bug) and we will see how Bug #7132 will be solved to avoid side effects like this. *** This bug has been marked as a duplicate of 6592 ***
Status: RESOLVED → VERIFIED
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Component: Profile Manager → Profile Manager BackEnd
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.