On Nov 15, 2007 2:37 PM, Greg Sieranski <greg.sieranski@xxxxxxxxxxxx> wrote: > > David Boles wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > André Costa wrote: > > > >> On Nov 15, 2007 12:21 PM, André Costa <blueser@xxxxxxxxx> wrote: > >> > >>> Hi Jouk, > >>> > >>> On Nov 15, 2007 11:31 AM, Jacob (=Jouk) Jansen > >>> <joukj@xxxxxxxxxxxxxxxxxxxx> wrote: > >>> > >>>> Andre wrote on 15-NOV-2007 13:39:22.26 > >>>> > >>>> > >>>>> My problem now is Mozilla plugins: Adobe Flash player doesn't work > >>>>> (nspluginwrapper fails to, well, wrap it, for some reason), and > >>>>> mplayer plugin downloads the whole movie but doesn't play it. If I > >>>>> save the movie and play it directly with either xine or mplayer it > >>>>> plays just fine (I tried with some trailers from > >>>>> http://www.apple.com/trailers) > >>>>> > >>>> Maybe it is the same problem as I had yesterday with internet radio > >>>> broadcasts : > >>>> -Look for which application is realy trying to play the movie. I guess it > >>>> is not the mplayer plugin but a libtotem plugin. If that is the case, > >>>> remove the plugin from /usr/lib64/mozilla/ directory and let the "real" > >>>> mplayer plugin do its work > >>>> > >>> Thks for the tip, but unfortunatelly that was not the case... > >>> > >>> Regards, > >>> > >>> Andre > >>> > >> Well, don't know if it's the proper way to solve this, but once I > >> replaced firefox.x86_64 with firefox.i386 (the same goes for > >> mplayerplug-in), and removed nspluginwrapper, all started working > >> again. > >> > >> The only (considerable) downside to it is that yelp depends on > >> firefox.x86_64, but so far I chose to lose it in favor of the 32bits > >> version of Firefox (I guess I could install 32bit version of yelp, but > >> I'm afraid it would demand tons of 32bit libs that I don't want laying > >> around). > >> > >> If anyone knows a better way of doing this (that would not force me to > >> remove yelp), please advise. > >> > > > > > > You did not have to remove the 64-bit Firefox. Just change the menu to > > point to the 32-bit Firefox. > > > > - -- > > > > > > David > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.7 (MingW32) > > > > iD8DBQFHPGoFAO0wNI1X4QERAp8wAJ4z086La2YcbpY0glIt/+6QPY7+CACePPED > > 5hKMUZ7JOnLCeQi+xg7qVdA= > > =35TP > > -----END PGP SIGNATURE----- > > > > > In the run application prompt you can use "firefox" for 64bit and > "firefox-32" for the 32 bit. That way you can keep both on your system. Hi Greg and David, thks for your tips. AFAICS there's no such a thing as "firefox-32" or anything like it. Just to make sure I reinstalled firefox.x86_64 alongside with .i386 version, and the only thing I get is /usr/bin/firefox, which is a bash script that will run 64bit version if it is available: ... ## ## Variables ## MOZ_ARCH=$(uname -m) case $MOZ_ARCH in x86_64 | ia64 | s390 ) MOZ_LIB_DIR="/usr/lib64" SECONDARY_LIB_DIR="/usr/lib" ;; * ) MOZ_LIB_DIR="/usr/lib" SECONDARY_LIB_DIR="/usr/lib64" ;; esac Since "uname -m" returns x86_64, this is the version that's always chosen. I could of course execute /usr/lib/firefox-2.0.0.9/firefox-bin directly, but everytime I upgrade firefox I will have to fix this reference. Am I missing something? Regards, Andre
