Firefox 4.0b9 fails to run due to XML Parsing Error: undefined entity (update.xul <wizard id="updateWizard"), with an own build

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
8 years ago
4 years ago

People

(Reporter: jeremyhu, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
Firefox 4.0b8 ran fine with the same configuration, but when I launch my freshly built 4.0b9, I get a window with the following:

XML Parsing Error: undefined entity
Location: chrome://mozapps/content/extensions/update.xul
Line Number 14, Column 1:
<wizard id="updateWizard"
^

Closing the window exists the application.  This is on darwin/x86_64 built with --disable-updater
Component: General → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: general → add-ons.manager
So I assume we fail because "updateWizard.title" is not defined? Don't we exclude update.xul from those builds?
Doubtful, we don't exclude the locale or xul files when building with --disable-updater. It is also very unclear how update.xul was opened since it has its own component that opens it that isn't built when building with --disable-updater. It could very well be the the startup cache wasn't cleared after building which would explain how a missing component was able to open the ui.

Where are you launching Firefox from?
(Reporter)

Comment 3

8 years ago
I am launching firefox from the command line with no arguments.
Where as where are you launching Firefox from? For example, from <obj-dir>/dist/bin or are you launching it from within a mac bundle? Does it also do this with a new profile?

Comment 5

4 years ago
Since this is a problem with a custom build, there's no point in keeping this open when reporter is unavailable -> WFM.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
Summary: Firefox 4.0b9 fails to run due to undefined updateWizard → Firefox 4.0b9 fails to run due to XML Parsing Error: undefined entity (update.xul <wizard id="updateWizard"), with an own build
You need to log in before you can comment on or make changes to this bug.