Right, I am really fed up with spending the entire festive season trying to install a stupid little plugin to make sounds comes out of Firefox. This should be easy I know but I just cannot work it out.

Object: Install mplayerplug-in in Firefox 1.0 on Suse 9.1

1. Tried to do it with YaST. Installed partially but not entirely, due to dependency issues (what use is that?)

2. Downloaded and tried to run mplayerplug-in-2.70-0.pm.2.i586.rpm, which is the correct .rpm. Four missing dependencies - 'libnspr4.so', 'libplc4.so', 'libplds4.so', 'libxpcom.so'. Couldn't find any of these in a Suse-based .rpm, and 'libxpcom.so' seems only to come as part of an entire reinstall of Mozilla.

3. Went back to YaST and followed instructions on dependency resolution. YaST tried to reinstall Firefox 0.8 from CD, so aborted.

4. Attempted a compile-from-source using the appropriate .tar.gz. Got to about the third hurdle before realising I was out of my depth.

5. ???

There must be an easier way to do this... mustn't there?

you have instaled Mplayer right
I usally let Kaffine do the config part it will display what it needs if theres any thing missing
get firefox 1.0x

If all else fails for you.
For Mplayer
Mplayers default folder for plugins is
/usr/local/lib/codecs
Just untar the codec package that you have and put it in the plugin folder. You may have to be root to do it. Check to see where your Mplayer plugin folder is.

For Firefox
If your install of Firefox is at
/usr/lib/firefox
Then untar the plugin and put it into Firefox's plugin folder which would be
/usr/lib/firefox/plugins

If you install the plugin into the Mozilla plugin folder than you can make a sym link to the plugin file in the firefox plugin folder.

If you don't know where Firefox is then at shell type
whereis firefox.
Firefox installs by default under your Home folder somewhere I think. If you can get the plugin library, put it into the plugin folder and it will work.

When you do this;
1. Extract source.
2. Run ./configure.
3. Run make.
4. Copy mplayerplug-in.so to your Mozilla-firefox plugins folder, and mplayerplug-in.xpt to your Mozilla-firefox components folder.
Where does it fail?

hi,

i'm assuming that you've installed firefox 1.0 from a firefox installer, ie not YaST, etc..

there are some basics that need to be addressed here, and it applies to any plugin that you wish to use with firefox...

the default install location for firefox 1.0 is, i think, your /home directory and the firefox plugin directory will be in a sub-directory; you therefore need to make sure that you either copy or sym link the plugins that you wish to use into the firefox plugin directory...

the suse mplayer-plugin rpms will (i think) be dependent on a complete suse installation of mozilla. this is ok - you can install mozilla alongside mozilla firefox, then just copy the plugin from the mozilla plugin directory to your firefox plugin directory. not the prettiest way of doing it, but it should work.

the mozilla fire fox website also gives some advice on the installation of common plugins -

http://plugindoc.mozdev.org/faqs/firefox-linux.html

good luck - it's worth it in the end.. and by the way, to make the most of the mplayer plugin, make sure you've got the essential mplayer win32 codecs installed - then you can play back pretty much all streaming media. the plugin works very well.

Thanks guys for all the pointers.

After far too many more hours of gnawing and googling on your collective advice I finally solved this rather simple problem.

comprookie2000 - compiling from source is prone to failure because (I have discovered) if you want to type "./configure" and not get about 17 error messages, then you need to have about 17 mysterious applications ("gecko-sdk", "pkg-config" plus more) already correctly installed and ready to go. Well, they are mysterious to me anyway.

kevinatkins - useful advice about the Mozilla install, that really clarified things. The solution was of course simple in the end. The .rpm had produced a file called "nsIScriptableMplayerPlugin.xpt", which was what made me think it hadn't worked properly. I just renamed this "mplayerplug-in.xpt" and put it in /.mozilla/plugins and everything worked fine. Why that worked I have no idea (and care even less, after that long spent installing a plug-in).

For anyone else hunting for leads on this question, check out -

http://mplayerplug-in.sourceforge.net/install.php
http://www.linuxquestions.org/questi...294#post886294

Having teething problems with certain sites, but this should be solvable.