After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 149812 - Galeon 1.3.17 no longer sees plugins in /usr/lib/mozilla/plugins/
Galeon 1.3.17 no longer sees plugins in /usr/lib/mozilla/plugins/
Status: RESOLVED FIXED
Product: galeon
Classification: Deprecated
Component: Mozilla interaction
1.3.17
Other Linux
: Normal normal
: 1.3.18
Assigned To: Philip Langdale
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2004-08-10 13:38 UTC by D. D. Brierton
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description D. D. Brierton 2004-08-10 13:38:37 UTC
The latest galeon only seems to see plugins installed into
/usr/lib/mozilla-1.7.2/plugins/, and not those in /usr/lib/mozilla/plugins/
whereas the previous version would. The latest versions of Mozilla and Epiphany
from Fedora Updates do see the Flash, Java and Real Player plugins, as well as
Mozplugger, whereas about:plugins in Galeon just sees libnullplugin.so.

I'm assuming that this is due to the removal of the startup script in this
version of Galeon.

Details:

$ ls -d /usr/lib/moz*
/usr/lib/mozilla        /usr/lib/mozilla-1.6    /usr/lib/mozilla-1.7.2

$ ls /usr/lib/mozilla/plugins/
flashplayer.xpt    libjavaplugin_oji.so  nphelix.so
libflashplayer.so  mozplugger.so         nphelix.xpt

$ ls /usr/lib/mozilla-1.6/plugins/
flashplayer.xpt  libflashplayer.so

$ ls /usr/lib/mozilla-1.7.2/plugins/
libnullplugin.so

$ rpm -qa | grep mozilla | sort
mozilla-1.7.2-0.2.0
mozilla-chat-1.7.2-0.2.0
mozilla-devel-1.7.2-0.2.0
mozilla-dom-inspector-1.7.2-0.2.0
mozilla-j2re-1.4.2-9.1.fc2.dag
mozilla-js-debugger-1.7.2-0.2.0
mozilla-mail-1.7.2-0.2.0
mozilla-nspr-1.7.2-0.2.0
mozilla-nspr-devel-1.7.2-0.2.0
mozilla-nss-1.7.2-0.2.0
mozilla-nss-devel-1.7.2-0.2.0

$ rpm -q epiphany
epiphany-1.2.7-0.2.0

$ rpm -q galeon
galeon-1.3.17-1.1.fc2.dag

$ rpm -qa | grep j2re | sort
j2re-1.4.2-8.1.fc2.dag
mozilla-j2re-1.4.2-9.1.fc2.dag

$ rpm -q RealPlayer
RealPlayer-10.0.0.297-20040730

$ rpm -q flash-plugin
flash-plugin-7.0.25-1

$ rpm -q mozplugger
mozplugger-1.5.2-1
Comment 1 Crispin Flowerday (not receiving bugmail) 2004-08-10 14:43:58 UTC
Galeon, as distributed by us, has never done anything special with the plugins.
However the dag rpm has a different wrapper script from the offical one, that
used to set the MOZ_PLUGIN_PATH env variable.

As there is no longer a wrapper script, you will need to set that environment
variable manually, or just copy the plugins to ~/.mozilla/plugins.
Comment 2 Christian Krause 2004-09-26 15:49:03 UTC
@Crispin:

This is not 100% true. As stated in doc/C/plugins.xml:
"    Galeon uses Mozilla's plugins located in ~/.mozilla/plugins,
    /usr/lib/mozilla/plugins or $MOZILLA_FIVE_HOME/plugins.
    To add a new plugin, copy or symlink the plugin into
    this directory.
"
galeon should look without any additional environment variables or something
like that in /usr/lib/mozilla/plugins for plugins.

It would be very nice if galeon could behave like the documentation. This would
be a very good solution, because nobody has to deal with setting variables or
linking plugins. 
Comment 3 Christian Krause 2004-09-30 18:55:52 UTC
Hi,

Unfortunately I got now answer to my comment. I ask you nicely again to reopen
the bug until either the behaviour or the documentation is fixed.

There was a discussion on the mailinglist
http://sourceforge.net/mailarchive/forum.php?thread_id=5296852&forum_id=6200
and it seems, that there won't any change in galeon. So please update the
documentation to something like this:

"
Galeon uses Mozilla's plugins located in the standard plugin search paths of
mozilla (~/.mozilla/plugins and $MOZILLA_FIVE_HOME/plugins). If you have a
common directory for plugins (e.g./usr/lib/mozilla/plugins) you should set the
MOZ_PLUGIN_PATH appropriate(e.g.
$MOZ_PLUGIN_PATH="$MOZILLA_FIVE_HOME/plugins:/usr/lib/mozilla/plugins"
)
To add a new plugin, copy or symlink the plugin into one of these directores or
extend MOZ_PLUGIN_PATH.
"

Thanks.
Christian 
Comment 4 Crispin Flowerday (not receiving bugmail) 2004-09-30 19:05:20 UTC
Sorry, I have the last bugzilla email sitting in my inbox, so I hadn't forgotten
about it :-)

I've been thinking about this, and am wondering whether it might not be best to
just put a putenv() call in  the moz_embed_shell() startup code to load plugins
from /usr/lib/mozilla, 

philipl, any thoughts ?
Comment 5 Christian Krause 2004-09-30 19:32:34 UTC
Thanks for reopening.

I suggest that you should get the variable first with getenv and extend it with
the /usr/lib/mozilla/plugins path. Otherwise you would ignore a user's decision
to put his plugins into /home/user/my_cool_plugins and set the MOZ_PLUGIN_PATH
appropriate.

Just my 2 cents...
Comment 6 Philip Langdale 2004-10-01 02:29:53 UTC
Crispin, this seems like a reasonable idea to me. Of course, it would be a
little nicer to to $MOZILLA_FIVE_HOME/plugins but as we don't have
$MOZILLA_FIVE_HOME... :-)
Comment 7 Crispin Flowerday (not receiving bugmail) 2004-10-02 17:41:50 UTC
I have fixed this in CVS, we will now look at:

$MOZ_PLUGIN_PATH:~/.mozilla/plugins:/usr/lib/mozilla/plugins:$MOZILLA_FIVE_HOME/plugins

http://lists.gnome.org/archives/cvs-commits-list/2004-October/msg00325.html