Fails to launch with XML parsing error

VERIFIED FIXED

Status

()

Core
XML
--
blocker
VERIFIED FIXED
16 years ago
16 years ago

People

(Reporter: tracy, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

({smoketest})

Trunk
smoketest
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
seen on commercial trunk builds:

windows 2003-01-06-04-trunk
linux 2003-01-06-04-trunk
mac os9 2003-01-06-03-trunk
mac osx 2003-01-06-04 -trunk

-use either full of stub installer
the build installs and goes to splash screen but soon after fails to launch with
the following error:


I back tested linux:  This did not happen with Fridays 2003-01-03-05-trunk
build.  But it did happen with Saturdays 2003-01-04-04-trunk build.  This has
been broken all weekend.
XML Parsing Error: undefined entity
Location : chrome://communicator/content/profile/profileSelection.xul
Line Number 40, Column 1:

-closing that window brings up another:

XML Parsing Error: undefined entity
Location : chrome://navigator/content/navigator.xul
Line Number 46, Column 1:

Comment 1

16 years ago
this seems to be a commercial build problem only. we should do smoketests on the
mozilla builds while we track this down.
it might be the landing (on friday?) that changed
chrome:localeVersion="1.2" -> chrome:localeVersion="1.3b" 
in just the mozilla tree.  (ns has not changed.)

I'll look into it.
Assignee: heikki → sspitzer
(Reporter)

Comment 3

16 years ago
confirming with windows commercial builds that this happened sometime between
2003-01-03-08-trunk and 2003-01-04-04-trunk   

note: The Activation screen popped up between the two error message windows
originally mentioned here when I tested the 01/04 build.

Comment 4

16 years ago
bloody localeVersion! thanks, seth. respinning with the updated rdf files.

Comment 5

16 years ago
Looks like you've already isolated it, but in testing on Linux, the 1/3 8am
trunk build was ok, but the 1/3 9pm build had the parsing error. So something
that checked in before the 9pm build seems to have caused it. Hope this helps.
(Reporter)

Comment 6

16 years ago
 windows commercial respin 2003-01-06-08-trunk launches fine.

marking fixed

will confirm other platforms as they become available.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
(Reporter)

Comment 7

16 years ago
verified with commercial respins on:

linux 2003-01-06-10-trunk
mac os9 2003-01-06-11-trunk
mac osx 2003-01-06-11-trunk
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.