Tip: See these twoarticles for an explanation of the differences between Stable/Beta/Dev, as well as Chromium vs. Chrome and the version numbers.

SRWare Iron, a modified Chromium with altered settings to increase privacy and with built-in ad-blocker, can be installed with the package iron-binAUR, available in the AUR.

Configuration

File associations

Unlike Firefox, Chromium does not maintain its own database of mimetype-to-application associations. Instead, it relies on xdg-open to open files and other mime types and URI schemes, for example, magnet links. There are exceptions to this rule though, for example in the case of mailto URIs, Chromium calls xdg-email, which is also part of xdg-utils package.

Font rendering

Chromium is now supposed to use the settings in ~/.fonts.conf, though you may have to edit it manually (see Font Configuration).
If your fonts setting are stored in another place, create ~/.fonts.conf and add these lines:

Tips and tricks

Troubleshooting

Proxy settings

There have been many situations in which proxy settings do not work properly, especially if set through the KDE interface. A good method as of now is to use Chromium's command-line options, like --proxy-pac-url and --proxy-server, to set your proxy.

Default profile

If you cannot get your default profile when you try to run Chromium and get a similar error instead:

You have to set the correct owner of the directory ~/.config/chromium as following:

# chown -R yourusername:yourusergroup ~/.config/chromium

WebGL

Sometimes, Chromium will disable WebGL with certain graphics card configurations. This can generally be remedied by typing about:flags into the URL bar and enabling the WebGL flag. You may also enable WebGL by passing 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, pass the flag --ignore-gpu-blacklist when starting Chromium, alternatively, go to about:flags and enable Override software rendering list.

Pulseaudio, PA-Alsa-Bridge and Pepper-Flash

Given a certain version of Chrome (23.x seem to exhibit this problem) and Pepper-Flash (11.x) while using the PA-Alsa-Bridge, sound may not play, become distorted, start skipping or outright keep crashing the PA-Alsa-Bridge continously. See [1] for the bugreport.

A possible workaround is to use pasuspender to suspend Pulseaudio and force Chrome to use Alsa directly.

First, create an ~/.asoundrc file to default Alsa to your real hardware instead of Pulseaudio. See Alsa and [2] for more information. Exemplary ~/.asoundrc:

~/.asoundrc

pcm. !default {
type hw
card 0
device 0
}

Then use pasuspender to suspend Pulseaudio and force Chrome to use Alsa which now uses your real hardware.

Google Play and Flash

DRM content on Flash still requires HAL to play. This is readily apparent with Google Play Movies. If one attempts to play a Google Play movie without HAL, they will receive a YouTube-like screen, but the video will not play.

Force 3D acceleration in Pepper Flash Player and i.g. the browser with radeon driver

To force 3D rendering there is an option "Override software rendering list" in chrome://flags, also you would have to export video acceleration variables, see ATI#Enabling_video_acceleration. You could check if it is working in chrome://gpu.