Closed Bug 15037 Opened 20 years ago Closed 20 years ago

[DOGFOOD]Create default profile if automigration of 1 profile fails

Categories

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

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: selmer, Assigned: dbragg)

Details

(Whiteboard: [PDT-])

In the case where we're automatically migrating a single 4.x profile, we need to
handle the error cases by creating a new default 5.0 profile to use.  We already
have a bug to show them error dialogs during migration, so this may not need its
own dialog.
Status: NEW → ASSIGNED
Target Milestone: M12
Dogfood Candidate
Summary: Create default profile if automigration of 1 profile fails → [DOGFOOD]Create default profile if automigration of 1 profile fails
Whiteboard: [PDT-]
Target Milestone: M12 → M13
Will fix by the dogfood deadline.
Moving TFV to M13.
Target Milestone: M13 → M14
Blocks: 22176
Severity: normal → minor
This would be good to get into the beta, but it's not critical.  Only work on
this after all the other M14 bugs are done.
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component.
Profile Manager component to be deleted.
A profile named "default" gets created if the automigration fails for the 
reasons like didn't find 4x profile directory to move contents from and other 
failures. Marking fixed.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
automigration fails, (4.x profile was renamed so 5.0 would not find it), mozilla 
crashes (mozilla build 2000020709) with a page fault in nsprefm.dll-
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Looks like a migration problem. 
As this is a crash, the program couldn't continue and hence there
is no chance to create a default profile.
Crash in nsprefm.dll suggests that some problem with migration module.
Assigning it to Don.
Assignee: racham → dbragg
Status: REOPENED → NEW
I'm a little unclear on what happened.  Are you saying that after the crash, the 
4.x profile wasn't there anymore?  Also was there no 5.x profile (even an 
incomplete one)?

We shouldn't be renaming any profiles.  Yes, a new one should have been created 
that was 5.0 specific but the 4.x one should still have been available.  Also, 
the registry isn't updated until nsprefm.dll returns to the profile code so a 
crash in nsprefm.dll should have prevented the registry from being updated.  
This would cause 5.0 to not see a new profile and thus try to auto migrate again 
the next time you started the program.

Accepting but need more information.  I'll talk to you about this Grace.
Status: NEW → ASSIGNED
4.x profile still exists with new name-renamed for testing only
I can show you what happens
Don,
Tested this on commercial build today and it is working as noted-default gets 
created when automigration fails. No crashes-
You can mark fixed 
Grace
Marking fixed per Grace.  (I think this was actually an XPCOM-related issue but 
I can't prove it.)
Status: ASSIGNED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
ok
Status: RESOLVED → VERIFIED
No longer blocks: 22176
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.