Closed Bug 257997 Opened 20 years ago Closed 20 years ago

extension makes firefox fail to start (mixed case in chrome path)

Categories

(Toolkit :: Add-ons Manager, defect)

1.7 Branch
x86
Linux
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 132183

People

(Reporter: ted, Assigned: bugs)

References

Details

Attachments

(3 files)

Someone on #firefox was trying to figure out why installing his extension was
making firefox fail to start.  Even in safe mode, with this extension installed,
Firefox refuses to start.

Possibly relevant lines from the log:
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsChromeRegistry.cpp,
line 624
WARNING: chrome: failed to get base url for
chrome://vssdoclinks/content/vssDocLinksOverlay.xul -- using wacky default, file
nsChromeRegistry.cpp, line 534

I'll attach the whole console log and the offending xpi following this.
Warning: will probably screw your profile
Seems to be choking on the overlay, but I could be wrong.
Further testing from the user shows that the problem was his using mixed case
for the chrome path.  Changing it from vssDocLinks to vssdoclinks makes this
problem go away.

I would still like it if this didn't break Firefox to the point where safe mode
doesn't work.
Blocks: 248125
Summary: extension makes firefox fail to start → extension makes firefox fail to start (mixed case in chrome path)
The problem, as I understand, is the same as Mozilla bug 132183. Do you agree, Ted?

(at least when I made two testcases for this bug, they both failed on Mozilla too).
Sounds about right.

*** This bug has been marked as a duplicate of 132183 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: