Browser plugins

From ArchWiki
Revision as of 13:23, 19 May 2011 by Wooptoo (talk | contribs) (Troubleshooting)
Jump to navigation Jump to search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

These plugins work in Firefox, Opera and WebKit derivatives.

Flash Player

Adobe Flash Player


Flash Player is in [extra]:

# pacman -S flashplugin


Adobe dropped x86_64 support for Flash for version 10.1. You can either install the 64-bit Template:Package AUR or get the stable 32-bit plugin (with nspluginwrapper) from the [multilib] repository (Install 32bit Flash on a 64bit System).


In addition, it may be needed to install Template:Package AUR from the AUR in order to properly render text.

If you are using a flashplugin from multilib and still having problems, e.g., fullscreen doesn't work, try to install lib32-your-driver-utils. Here's an example for nvidia card users:

# pacman -S lib32-nvidia-utils

This will replace your driver-utils with the lib32-driver-utils.


To change general plug-in preferences (privacy settings, resource usage, etc.), right click on embedded Flash content and choose preferences from the menu, or go to the Macromedia website. There, a Flash animation will give access to local settings.

You can make your own mms.conf settings for flash, just the dir /etc/adobe and put mms.cfg in there. Example config below

 # Adobe player settings
 AVHardwareDisable = 0
 FullScreenDisable = 0
 LocalFileReadDisable = 1
 FileDownloadDisable = 1
 FileUploadDisable = 1
 LocalStorageLimit = 1
 ThirdPartyStorage = 1
 AssetCacheSize = 10
 AutoUpdateDisable = 1
 LegacyDomainMatching = 0
 LocalFileLegacyAction = 0
 AllowUserLocalTrust = 0
 # DisableSockets = 1 
 OverrideGPUValidation = 1

Flash leaks on other pages with a nvidia card

If flash animations "leak" on other webpages with chromium or firefox, you can try to turn off hardware acceleration in mms.cfg file and/or in the flash parameters dialogue. See

PDF viewer


if you want to see a pdf in firefox without open a new window follow this guide:

Adobe Reader

Due to licensing restrictions, Adobe Reader cannot be distributed from any of the official Arch repositories. There are versions available in the AUR. Please note that no matter how many votes it receives, this package will never be included in the [community] repository. See this comment for an explanation.

Also, there are localizations available in many languages.


32-bit AUR package: Template:Package AUR

It installs the Acrobat Reader application as well as the Firefox plugin. Note that hardware-assisted rendering is unavailable under Linux (at least using a Geforce 8600GTS with driver version 185.18.14).


Adobe Reader is a closed-source application, meaning that users desiring a 64-bit binary have no other choice other than to wait for official support. Workarounds to be considered:

  • Follow this guide originally posted in the forums. It involves creating a chrooted environment that could be reused for other 32-bit only applications.
  • Or, simply get the 32-bit binary along with the 32-bit dependencies. Install Template:Package AUR. Also, consider installing the extra font packages suggested by the package. Be advised that the Firefox plugin cannot be used directly with this binary -- it will not load in the 64-bit browser. Template:Package AUR is required to load the plugin. Finally, be sure to run:
$ nspluginwrapper -v -a -i

as a normal user. This checks the plugin directory and links the plugins as needed. Everything should work as expected now.


See: Citrix



# pacman -S openjdk6 icedtea-web

Weird symlink

Either Java package contains the Java runtime as well as the fitting browser-plugin.

# pacman -S openjdk6

Or install the proprietary version of Java:

# pacman -S jre

Keep in mind that the open-source and closed-source versions cannot be installed in parallel. The open-source version is nearly perfect at the time of writing and there is mostly no need anymore to install the proprietary version of Java. But if you want to, since firefox v.3.6 does not seem to look in /usr/lib/mozilla/plugins, which is the default location where jre v.1.6.0_22 place the java plugin, just

# cd to ~/mozilla/plugins
# ln -s /opt/java/jre/lib/i386/

and it is safe to

# rm -R /usr/lib/mozilla

unless you use it for something else! Be careful here.

Video Plugins

Gecko Media Player

A good replacement of the now obsolete mplayer-plugin is Gecko Media Player. More stable combined with MPlayer 1.0RC2. (No more crashes with Apple Trailers.)

# pacman -S gecko-mediaplayer

Totem Plugin

The Template:Package Official might be the choice for those seeking a gstreamer-based plugin:

# pacman -S totem-plugin

VLC Plugin

This plugin use VLC to play video:

# pacman -S vlc-plugin



Install Template:Package AUR through the AUR.


Browser does not acknowledge flash plugin / Permission errors

If the browser does not seem to detect the plugin, for example; about:plugins in Firefox does not display Template:Filename, check the permissions on the Template:Filename, Template:Filename directories, and on Template:Filename itself.

Check the permissions with:

$ ls -la /usr/lib/mozilla

The correct permissions can be applied with:

# chmod -R 755 /usr/lib/mozilla

Flash blocks sound and/or delayed playback

If sound is delayed within flash video and/or if Flash stops sound from any other application, then:

# vim /etc/rc.conf

Locate the Template:Codeline array and add Template:Codeline to banned modules, which should look like:

MODULES=( !snd-pcm-oss )

No sound in Flash

Flash Player outputs its sound only through the default ALSA device, which is number 0. If you have multiple sound devices (a very common example is having a sound card and HDMI output in video card), then your preferred device may have a different number. For example:

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: DX [Xonar DX], device 0: Multichannel [Multichannel]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: DX [Xonar DX], device 1: Digital [Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

In this case, HDMI output is "card 0" and sound card is "card 1". To make it default for ALSA, create a file named Template:Filename with the following content:

pcm.!default {
type hw
card 1

ctl.!default {
type hw
card 1

No sound in Flash with OSSv4

If you use OSSv4 on x86_64 with the multilib Template:Codeline you should install the Template:Codeline library:

# pacman -S lib32-libflashsupport

No sound in Flash with jack/x86_64/multilib

If you use jack-audio-connection-kit on x86_64 with the multilib Template:Codeline you should install the Template:Codeline from AUR. To make this work you will also need lib32-alsa-plugins, which is not listed as a lib32-libflashsupport-jack dependancy.

# pacman -S lib32-alsa-plugins

Flash performance

Adobe's Flash plugin has some serious performance issues, especially when CPU frequency scaling is used. There seems to be a policy not to use the whole CPU workload, so the frequency scaling governor does not clock the CPU any higher. To work around this issue, see: cpufrequtils#Changing the ondemand governor's threshold

Plugins are installed but not working

A common problem is that the plugin path is unset. This typically occurs on a new install, when the user has not re-logged in before running Firefox after the installation. Test if the path is unset:


If unset, then either re-login, or source Template:Filename and start Firefox from the same shell:

. /etc/profile.d/ && firefox

Gecko Media Player Won't Play Apple Trailers

If Apple Trailers appear to start to play and then fail, try setting the user agent for your browser to:

QuickTime/7.6.2 (qtver=7.6.2;os=Windows NT 5.1Service Pack 3)

Low webcam resolution in Flash

If your webcam has low resolution in Flash (the image looks very pixelated) you can try starting your browser with this:

LD_PRELOAD=/usr/lib/libv4l/ chromium