Closed
Bug 595552
Opened 14 years ago
Closed 13 years ago
Could not read chrome manifest file
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 654720
People
(Reporter: bugzilla, Unassigned)
Details
Don't know where this fits in, but at the moment we get the following messages in the error console after startup.
Could not read chrome manifest file '$objdir/mozilla/dist/bin/components/toolkitsearch.manifest'.
Could not read chrome manifest file '$objdir/mozilla/dist/bin/distribution/bundles/mochitest/chrome.manifest'.
Could not read chrome manifest file '$objdir/mozilla/dist/bin/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}/chrome.manifest'.
The last one is related to bug 586610.
|
Reporter | |
Comment 1•14 years ago
|
||
With the Mozilla/5.0 (Windows NT 5.1; rv:2.0b6pre) Gecko/20100908 Firefox/4.0b6pre SeaMonkey/2.1b1pre nightly, I only get the last message about our theme. The first one could be an issue with my self compiled build, the second due to it being a debug build.
|
||
Comment 2•13 years ago
|
||
Feel free to revert the duping if you care about the first two.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•