Closed Bug 195229 Opened 23 years ago Closed 23 years ago

Fails to launch with XML Parsing Error

Categories

(Core Graveyard :: Profile: BackEnd, defect)

defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: tracy, Assigned: ccarlen)

Details

(Keywords: smoketest)

seen with commercial trunk builds: windows 2003-02-27-04-trunk linux 2003-02-27-05-trunk -install build -launch the build the installation fails to launch with the following error: XML Parsing Error: undefined entity Location: chrome://communicator/content/profile/profileSelection.xul Line Number 40, Column 1: <windows ^
also on mac 2003-02-27-03-trunk I believe 195203 is a dupe...he's reporting about shared libs, but that is another bug.
this is not on the mozilla trunk. mozilla builds install and launch fine. closing invalid for mozilla. opened bugscape 22765
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
verified
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.