(Add note on SELinux) |
|||
| Line 22: | Line 22: | ||
===== Checking the plugin ===== | ===== Checking the plugin ===== | ||
Following the installation for either architecture, start Firefox and type in the addressbar: | Following the installation for either architecture, start '''Firefox''' and type in the addressbar: | ||
<pre> | <pre> | ||
about:plugins | about:plugins | ||
| Line 32: | Line 32: | ||
This tells you that Adobe's flash player has been successfully installed. | This tells you that Adobe's flash player has been successfully installed. | ||
===== SELinux problems ===== | |||
In some cases, {{{nspluginwrapper}}} produces SELinux AVC errors, some of which may prevent viewing Flash content. Changing the default SELinux booleans may resolve this problem, but eliminates a great deal of security when using {{{nspluginwrapper}}}: | |||
<pre> | |||
su -c 'setsebool -P allow_unconfined_nsplugin_transition=0' | |||
</pre> | |||
Revision as of 15:26, 19 November 2008
Enabling Flash Plugin
For i386
Unlike earlier releases, no special steps are required to install the proprietary Adobe Flash Player 10 on Fedora 10 for i386. Simply follow the steps on Adobe's download page.
For X86_64
Select the YUM version of the Adobe Flash Player from Adobe's download page. This installs Adobe's software repository so that updates can be applied by the normal Fedora update process.
Next some helper files are needed in addition to the Flash Player:
su -c 'yum install flash-plugin nspluginwrapper.i386 \
alsa-plugins-pulseaudio.i386'
You will need to authorize Adobe's key during the install.
After the installation, exit all copies of Firefox to enable the plugin.
Checking the plugin
Following the installation for either architecture, start Firefox and type in the addressbar:
about:plugins
You should see a section similar to the following:
This tells you that Adobe's flash player has been successfully installed.
SELinux problems
In some cases, {{{nspluginwrapper}}} produces SELinux AVC errors, some of which may prevent viewing Flash content. Changing the default SELinux booleans may resolve this problem, but eliminates a great deal of security when using {{{nspluginwrapper}}}:
su -c 'setsebool -P allow_unconfined_nsplugin_transition=0'