Closed Bug 14239 Opened 26 years ago Closed 26 years ago

Profile Manager should confirm existance of profile dir

Categories

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

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: ppandit, Assigned: racham)

Details

Using a debug build on Windows NT. The profile manager should check for the existance of the profile before trying to open it 1) Create a pop account profile in 4.7 called "earthlink" 2) del C:\winnt\moz*.dat 3) Migrated over the pop profile 4) Ran across a problem that I did not understand so I decide to start over 5) Deleted the directory \mozill\dist\users50\earthlink 6) Forgot to del c:\winnt\moz*.dat 7) Started apprunner -installer and selected earthlink (no migration tag since it was already migrated) 8) Got a crash since no profile existed
Assignee: selmer → racham
Summary: Profile Manager should confirm existance of profile → Profile Manager should confirm existance of profile dir
Bhuvan, I thought this was a dup, but I can't find the bug to dup against. Was this fixed already once?
Bhuvan, bug 13719 looks similar, both involving migrating an already migrated profile
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
I just tried to reproduce the scenario. It creates the (profile) folder that is being deleted. A profile dir with profile name gets created under Users50 folder with default contents in it. This problem is fixed while ago. However, other changes mozilla might have caused inconsistencies. So, please try with latest builds.
Product: MailNews → Browser
QA Contact: lchiang → gbush
Status: RESOLVED → VERIFIED
tested with build 1999092308 and found same behavior as noted below, new directory(same name as deleted) was created and populated with a default profile.
Component: Profile Manager → Profile Manager BackEnd
Moving all Profile Manager bugs to new Profile Manager Backend component. Profile Manager component to be deleted.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.