- 1 Installation
- 2 Configuration
- 3 Tips and tricks
- 4 Troubleshooting
- 5 See also
- AUR - the development version (binary version: AUR)
- AUR - the beta version
- AUR - the development version
32-bit systems predating SSE2
As of version 35 of chromium, support for older hardware without an SSE2 instruction set has been removed upstream. Users of old hardware still wishing to use chromium may build the AUR package or download a pre-compiled package from Repo-ck#Miscellaneous_packages. Keep in mind that requiring SSE2 fixed several bugs, and you should not report issues encountered with this patched version upstream.
Set Chromium as default browser
Flash Player plugin
pepper-flash is the Flash Player plugin, using the new Pepper plugin API. It is developed by Adobe, and distributed bundled with Google Chrome.
To install pepper-flash for Chromium, install AUR. If you want the development version, install AUR.AUR from the
Enable the plugin in
PDF viewer plugin
There are multiple ways of enabling PDF support in Chromium that are detailed below.
libpdf is Google's own implementation of a PDF renderer included with Google Chrome. It is compatible with Chromium.
To install libpdf for Chromium, install AUR. If you want the development version, install AUR.AUR from the
Enable the plugin in
See the main article: Browser plugins#PDF.js
The print preview feature is disabled by default in Chromium, unlike Google Chrome. Enabling it requires passing
--enable-print-preview with the #PDF viewer plugin installed.
Chromium uses NSS for certificate management. Certificates can be managed in
Show advanced settings... →
Tips and tricks
See the main article: Chromium tweaks
Constant freezes under KDE
There have been reports of cracking sound with chromium over hdmi audio. Start chromium with a different audio buffer size to fix the issue:
$ chromium --audio-buffer-size=2048
As of June 2012, there are many situations in which proxy settings do not work properly, especially if set through the KDE interface. A working alternative is to use Chromium's command-line options, like
--proxy-server, to set your proxy.
Chromium will sometimes disable WebGL with certain graphics card configurations. To remedy this, enter
chrome://flags into the URL bar and disable the Disable WebGL flag. Alternatively, pass the command line flag
--enable-webgl to Chromium in the terminal.
There is also the possibility that your graphics card has been blacklisted by Chromium. To override this use the go to
chrome://flags and enable the Override software rendering list flag. Alternatively, pass the command line flag
--ignore-gpu-blacklist to Chromium in the terminal.
If you're using Chromium with Bumblebee, WebGL might crash due to GPU sand-boxing. In this case, you can disable GPU sand-boxing with
optirun chromium --disable-gpu-sandbox.
Force 3D acceleration in Flash Player and the browser
First, make sure you have all the required packages as explained in VDPAU. Then, to force 3D rendering enable the flag "Override software rendering list" in
chrome://flags. Check if it is working in
speech-dispatcher dumps core
Chromium installsas a dependency. The latter is an independent layer for speech synthesis interface and by default uses as its back end. If you are frequently receiving core dumps, it is likely caused by not having installed festival. To resolve the error message, either install festival or change the back end used by speech-dispatcher.