On 05/29/2008 03:26 AM, Simon Roberts wrote:
Then I reinstalled from Yast, just firefox and flash-plugin-9.0.124.0-release
Then I did "rpm -q -filesbypkg flash-plugin-9.0.124.0-release" to determine the name of the actual plugin file (which was reported as /usr/lib/flash-plugin/libflashplayer.so)
Then I used "nspluginwrapper -i /usr/lib/flash-plugin/libflashplayer.so" to get the wrapper to notice the 32-bit driver
Then I restarted firefox, and it works a treat :) It does seem to be generating some warning messages to stderr, but these don't seem to prevent it from working properly
Thanks to all who've helped (and yes, I'm still interested in why this didn't work out of the box, and in helping find out for the benefit of future generations :)
That isn't the way it works normally. Browser plugins are installed to /usr/{_lib}/browser-plugins. So, joe@jmorris:~> rpm -qf /usr/lib/browser-plugins/libflashplayer.so flash-player-9.0.124.0-0.1 joe@jmorris:~> rpm -qa | grep flash flash-player-9.0.124.0-0.1 nspluginwrapper automatically installs, I believe via a post-install script, the plugins it finds in the 32 bit location, i.e. /usr/lib/browser-plugins. Since you installed something that did not install in the default location, i.e. a non suse package according to pin, you needed to setup nspluginwrapper manually. If you would have installed the flash-player from the install media (which would have been upgraded via online update), it would have worked out-of-the-box.
-- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org