Install adobe flash-plugin in Fedora 13_x64

Refer to:

http://fedoraproject.org/wiki/Flash

http://bbs.fedora-zh.org/showthread.php?5222-Fedora-X86_64%E5%AE%89%E8%A3%85flash-plugin

su -c 'yum install nspluginwrapper.{x86_64,i686} alsa-plugins-pulseaudio.i686 --disablerepo=adobe-linux-i386'



su -c 'yum install flash-plugin'







[frank@apollo svn_imsdroid]$ su -c 'yum install nspluginwrapper.{x86_64,i686} alsa-plugins-pulseaudio.i686 --disablerepo=adobe-linux-i386'



Password: 



Loaded plugins: presto, refresh-packagekit



Setting up Install Process



Package nspluginwrapper-1.3.0-13.fc13.x86_64 already installed and latest version



Package nspluginwrapper-1.3.0-13.fc13.i686 already installed and latest version



Package alsa-plugins-pulseaudio-1.0.22-1.fc13.i686 already installed and latest version



Nothing to do



[frank@apollo svn_imsdroid]$ su -c 'yum install flash-plugin'



Password: 



Loaded plugins: presto, refresh-packagekit



Setting up Install Process



Package flash-plugin-10.1.102.65-release.i386 already installed and latest version



Nothing to do











Then check the plugin by input "about:plugins" in address bar.



And open http://www.adobe.com/software/flash/about/ to check flash-plugin.

Installing the plugin on Chromium

Follow all of the instructions in the Enabling Flash Plugin section. Then:

- on 32-bit, create a symbolic link that tells Chromium how to find the 32-bit plugin:

sudo ln -s /usr/lib/mozilla/plugins/libflashplayer.so /usr/lib/chromium-browser/plugins/libflashplayer.so

- on 64-bit, create a symbolic link that tells Chromium how to find the 64-bit plugin:

- run Mozilla Firefox once so that it creates /usr/lib64/mozilla/plugins-wrapped/nswrapper_32_64.libflashplayer.so

sudo ln -s /usr/lib64/mozilla/plugins-wrapped/nswrapper_32_64.libflashplayer.so /usr/lib64/chromium-browser/plugins/nswrapper_32_64.libflashplayer.so

- Exit all Chromium windows and restart Chromium.

- In the Chromium address bar, type "about:plugins" to check whether the plugin loaded. You may have to re-run Chromium with the --enable-plugins command line switch to force Chromium to re-scan its plugins folder.