Crash when launching branch navonly build with classic theme profile

RESOLVED WORKSFORME

Status

P3
critical
RESOLVED WORKSFORME
18 years ago
11 years ago

People

(Reporter: agracebush, Unassigned)

Tracking

({crash, helpwanted, stackwanted})

Trunk
Future
x86
Windows NT
crash, helpwanted, stackwanted

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
Steps to reproduce:

1. using recommended or full install of limbo build, create or migrate a profile 
2. after launch change theme of that profile to classic
3. install navonly build and launch with the same profile

actual results: crash- always
expected results: launch with classic theme profile

so far win only

Comment 1

18 years ago
Changing summary, sending to skinability (skin switching issue).

Assignee: hangas → ben
Component: Themes → Skinability
QA Contact: pmac → blakeross
Summary: Crash when launching limbo navonly build with classic theme profile → Crash when launching branch navonly build with classic theme profile

Comment 2

18 years ago
I don't actively test the branch. QA -> patty
QA Contact: blakeross → pmac

Comment 3

18 years ago
Pretriage of skinnability bugs, marking nsbeta1-. Don't think we'll get to this 
for beta1
Keywords: nsbeta1-

Comment 4

18 years ago
Marking nsbeta1- bugs as future to get off the radar
Target Milestone: --- → Future

Updated

18 years ago
Severity: normal → critical
Keywords: crash
Mass move skinability bugs to nobody@mozilla.org, helpwanted. 
Assignee: ben → nobody
Keywords: helpwanted

Comment 6

17 years ago
Grace Bush: Can you reproduce this bug with a latest build?
Keywords: stackwanted
(Reporter)

Comment 7

17 years ago
latest build does not crash, able to launch with either theme
2002040903

Comment 8

17 years ago
Marking WFM regarding last reporter's comment.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

11 years ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.