Closed Bug 192647 Opened 21 years ago Closed 21 years ago

Switch profile when no second profile exists causes crash

Categories

(Core Graveyard :: Profile: BackEnd, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: raccettura, Assigned: ccarlen)

Details

(Keywords: crash, stackwanted)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210

When attempting to switch profile (Tools -> Switch profile...) leads to a crash
if there is no second profile present

Reproducible: Always

Steps to Reproduce:

Actual Results:  
Crash

Expected Results:  
said "no other profile exists
reporter: please use a talkback build and get a talkback incident id for your
crash (run bin\components\talkback.exe)
Assignee: jaggernaut → ccarlen
Severity: normal → critical
Component: Profile Manager FrontEnd → Profile Manager BackEnd
Keywords: crash, stackwanted
Windows XP, 1.3beta, etc, identical.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210

No crash using those steps. Profile manager just comes up, and WFM. No second
profile, etc.
WFM on Win98.
timeless:  oldest talkback incident ID on record (there are only 3) are newer
than the last time I experienced this issue.

Haven't seen it in the past few days, so it appears to be OK now.  Also did a
clean install.   Think it might have been linked to Bug 190484... perhaps a bad
installation caused this to occur.

Anyway, it hasn't happened in recent days, so I assume it's fine.  I will keep
testing it and report back any with talkback enabled if there is any issue
regarding this.  


P.S.:  Please accept my humble appologies for my lack of responce on this issue.
 Busy times.
marking worksforme (win2k and XP) per above comments
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.