Closed Bug 368819 Opened 19 years ago Closed 15 years ago

Extensions initialization failures should have better handling

Categories

(Firefox :: Extension Compatibility, defect)

2.0 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: mrl, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061115 Mandriva/2.0.0.1-5mdv2007.1 (2007.1) Firefox/2.0.0.1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1) Gecko/20061115 Mandriva/2.0.0.1-5mdv2007.1 (2007.1) Firefox/2.0.0.1 After instaling xforms extension in mozilla-firefox 2.0.0.1 shipped with current Mandriva Cooker we had a problem due a missing library on the system. FF is built against libstdc++6 and xforms plugin is linked against libstdc++5, which wasn't installed. The problem is that no error messages at all were shown in order to help identifying the problem. It would be good if we could at least see "Failed to load plugin <name>", so that we would know it failed on that stage. Reproducible: Always Steps to Reproduce: 1.Install an unloadable plugin due to missing symbols, for example 2.Restart firefox 3.Try to trigger it (opening a xhtml page, for example) Actual Results: No error messages are shown. Expected Results: Error messages clarifying the problem.
Maybe this bug should be renamed "Extensions initialization failures should have better handling" to get attention. As you know, plugins and extensions are two different things in Mozilla.
Ops, sorry. Thanks for the tip :)
Summary: Plugin initialization failures should have better handling → Extensions initialization failures should have better handling
Is this still a fault for the user with recent Firefox versions?
Version: unspecified → 2.0 Branch
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.