Closed Bug 24545 Opened 25 years ago Closed 25 years ago

[Dogfood] Commercial build fails to start up

Categories

(SeaMonkey :: General, defect, P1)

Product:
SeaMonkey
Component:
General
Platform:
All
Mac System 8.5
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: sfraser_bugs, Assigned: matt)

References

Details

today's commercial build is horked. It fails to start up because it cannot load
helpMenu.xul, which lives in chrome/global/content.

I note that there is an overlays.rdf in chrome/global/content, which specifies
helpMenu.xul as something that should be loaded. But should helpMenu.xul be in
chrome/global/content/default, instead of chrome/global/content?

Moving it to chrome/global/content/default fixes the problem.

Also (hyatt) should we really halt if a xul file specified in an overlays.rdf
cannot be found?
Priority: P3 → P1
Target Milestone: M13
Severity: normal → blocker
Summary: Commercial build fails to start up → [Dogfood] Commercial build fails to start up
jan, do lemme know if this already exists... :-)
I have a fix for this.
Putting in ManifestDefaults
Status: NEW → ASSIGNED
fixed
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
*** Bug 24404 has been marked as a duplicate of this bug. ***
*** Bug 24568 has been marked as a duplicate of this bug. ***
works using 2000-01-24-01-m13 comm bits (MacOS 9.0, btw). verifying as fixed.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
melo
Please don't spam old bugs. Please use landfill.bugzilla.org for testing.
You need to log in before you can comment on or make changes to this bug.