GNOME Bugzilla – Bug 541496
plugin should use xpcom glue mozilla/plugins/libtotem-complex-plugin-gstreamer.so: undefined symbol: _ZN13nsTArray_base9sEmptyHdrE
Last modified: 2008-07-04 09:36:22 UTC
https://bugzilla.mozilla.org/show_bug.cgi?id=443437 -- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052912 Firefox/3.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008052912 Firefox/3.0 LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/libtotem-complex-plugin-gstreamer.so [/usr/lib/mozilla/plugins/libtotem-complex-plugin-gstreamer.so: undefined symbol: _ZN13nsTArray_base9sEmptyHdrE] LoadPlugin: failed to initialize shared library /usr/lib/mozilla/plugins/libtotem-complex-plugin-gstreamer.so [/usr/lib/mozilla/plugins/libtotem-complex-plugin-gstreamer.so: undefined symbol: _ZN13nsTArray_base9sEmptyHdrE] Reproducible: Always Steps to Reproduce: firefox http://www.wpxi.com/video/16757372/index.html Actual Results: crashed and received mail mozilla bug report popup. It also failed with something like failed mail bug report. Expected Results: not a crash $ cat /etc/release Mandriva Linux release 2008.1 (Official) for i586 also failed on 2.0.0.14 -- This looks like a case where the browser plugin is linking against gecko directly instead of xpcom glue. Note that I can't tell if the original bug report is that the plugin triggered a crash (unlikely) or if it's about something else. This bug report is only interested in discouraging the listed plugin (and any created by the same team) from directly linking against mozilla libraries.
The fact that it crashes isn't a Totem problem. And we've already removed XPCOM usage in 2.23. *** This bug has been marked as a duplicate of 520629 ***