On Sunday 08 October 2006 15:55, Dave Howorth wrote:
IIRC, I've only loaded Firefox with YaST, because I hate this kind of problem. But perhaps I've forgotten something.
Same here. But I still end up with multiple apparent Firefox 'homes'. Maybe they're installed in parallel to accommodate legacy plug-ins or dependent packages? The 'lazy' approach I've described has always worked for me... ???
ls /opt/MozillaFirefox/lib/plugins/ . libjavaplugin_oji.so mplayerplug-in-rm.so .. libnullplugin.so mplayerplug-in.so flashplayer.xpt mplayerplug-in-gmp.so mplayerplug-in-wmp.so libflashplayer.so mplayerplug-in-qt.so nphelix.so nphelix.xpt nppdf.so ^^^^ This one's good (and my current 'active' Firefox install)
ls /opt/mozilla/lib/plugins/ . libnullplugin.so mplayerplug-in-qt.so mplayerplug-in.so .. mplayerplug-in-gmp.so mplayerplug-in-rm.so mplayerplug-in-wmp.so ^^^^ Here, as root: ln -s /usr/lib/browser-plugins/nppdf.so nppdf.so
ls /opt/mozilla/lib64/plugins/ . .. libnpflash.so libnullplugin.so mozplugger.so ^^^^ Not here, as you surmised, because nppdf.so is 32-bit
Well, I had:
/home/dhoworth/.mozilla/pluginreg.dat /home/dhoworth/.mozilla/firefox/pluginreg.dat
so I deleted them both, after checking Firefox wasn't running. But I still have the same problem.
Close Firefox. Create the symlink described above. Delete both copies of pluginreg.dat. Launch Firefox and test.
I'm tempted to just tell YaST to remove Firefox and Acrobat reader and then reinstall.
I'd try downloading and reinstalling these items manually from commandline. But that's me.
Thanks for the help, Carl.
You're welcome. If this doesn't work, there must be some kind of interaction happening as a result of the 64-bit <> 32-bit libraries and I'm out of ideas. Carl