Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 198058
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Linux Gnome Desktop Team <gnome@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Walter Meinl <wuno@lsvw.de>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
ei.txt emerge --info text/plain Walter Meinl 2007-11-04 14:38 0000 3.82 KB Details
totem-2.20.1-browser-plugins.patch patch removing the first hunk for configure.in (as it was in earlier versions of the patch) patch Walter Meinl 2007-11-21 23:20 0000 1.21 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 198058 depends on: Show dependency tree
Bug 198058 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-11-04 14:36 0000
From my .xsession-errors.
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-basic-plugin.so [libxpcom.so.1: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-complex-plugin.so [libxpcom.so.1: Kann
die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-gmp-plugin.so [libxpcom.so.1: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-mully-plugin.so [libxpcom.so.1: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-narrowspace-plugin.so [libxpcom.so.1:
Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht
gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-basic-plugin.so [libxpcom.so.1: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-complex-plugin.so [libxpcom.so.1: Kann
die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-gmp-plugin.so [libxpcom.so.1: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-mully-plugin.so [libxpcom.so.1: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden]
LoadPlugin: failed to initialize shared library
/usr/lib64/nsbrowser/plugins/libtotem-narrowspace-plugin.so [libxpcom.so.1:
Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht
gefunden]
translated libxpcom.so.1: cannot open shared object: file or directory not
found

Reproducible: Always

Steps to Reproduce:
1.emerge net-libs/xulrunner
2.emerge totem-2.20.1 with USE='nsplugin xulrunner'
3.

Actual Results:  
doesn't find libxpcom.so.1, though its present in /usr/lib/xulrunner

Expected Results:  
should find it

I don't see the totem-plugin in mozilla-firefox (about:plugins)
I don't have this problem when I build totem against mozilla-firefox
(USE=-xulrunner -seamonkey nsplugin)
I don't see the problem with media-video/totem-2.20.0

I'd guess it is somehow related either to the soname versioning of xulrunner or
to the totem-2.20.1-browser-plugins.patch.

------- Comment #1 From Walter Meinl 2007-11-04 14:38:48 0000 -------
Created an attachment (id=135149) [details]
emerge --info

------- Comment #2 From Gilles Dartiguelongue 2007-11-18 12:11:46 0000 -------
how do you expect plugins to be present in mozilla-firefox when you are
building against xulrunner ? firefox doesn't use (yet) xulrunner so you have to
choose what kind of browser you will use: firefox or xulrunner-based (epiphany)

------- Comment #3 From Daniel Gryniewicz 2007-11-21 17:20:16 0000 -------
No, that's not true.  Plugins are installed in a central location, and firefox
can find them fine.  At least, it's *supposed* to work.  I don't have firefox,
so I can't verify.

------- Comment #4 From Walter Meinl 2007-11-21 23:16:19 0000 -------
(In reply to comment #3)
> No, that's not true.  Plugins are installed in a central location, and firefox
> can find them fine.  At least, it's *supposed* to work.  I don't have firefox,
> so I can't verify.
> 
You're right, with totem-2.20.0 built against the same xulrunner-1.8.1.9 build
the plugins do work with firefox (and that's what I remembered from earlier
totem versions).
The failure to not find the plugins with 2.20.1 seems related to the
totem-2.20.1-browser-plugins.patch. When I remove the first hunk for
configure.in of the patch, firefox finds the totem plugins again.

------- Comment #5 From Walter Meinl 2007-11-21 23:20:42 0000 -------
Created an attachment (id=136644) [details]
patch removing the first hunk for configure.in (as it was in earlier versions
of the patch)

this is the updated patch that lets firefox find the plugins of totem built
against xulrunner. However in the log of the gentoo cvs I find a comment from
compnerd "add a hack to fix firefox runtime (Portage version: 2.1.3.12)" that
indicates that the line I removed should have fixed the same or another issue.

------- Comment #6 From Saleem Abdulrasool (RETIRED) 2007-12-16 04:36:56 0000 -------
Please try -r1.  It should work if you build with nsplugins + xulrunner as it
is now more strict about applying the xpcom hack (applies only with firefox).

------- Comment #7 From Walter Meinl 2007-12-16 13:03:15 0000 -------
(In reply to comment #6)
> Please try -r1.  It should work if you build with nsplugins + xulrunner as it
> is now more strict about applying the xpcom hack (applies only with firefox).
> 
Yes for totem-2.20.1-r1 it works, thanks.
However, in the overlay totem-2.21.5.ebuild the local $needs_xpcom_hack
construct doesn't work.The patch gets applied whatever USE flag I tried
(-xulrunner -seamonkey; -xulrunner seamonkey; xulrunner -seamonkey; -xulrunner
-seamonkey) though only the latter combination should do it. Probably the best
way would be to solve it like in the 2.20.1-r1 ebuild. Furthermore I found a
typo in the 2.21.5 ebuild 
if use tracker || use nsplugins ; then
should read
if use tracker || use nsplugin ; then 
otherwise you get with USE=-tracker : nsplugins is not in IUSE

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug