- 1 Installation
- 2 Configuration
- 3 Tips and tricks
- 4 Troubleshooting
- 5 See also
Other alternatives include:
- Chromium Beta Channel — the beta version
- Chromium Dev Channel — the development version
- Chromium snapshot builds — the untested nightly version
- https://build.chromium.org/ || AUR
- Chromium with VA-API support — with a patch to enable VA-API
Other alternatives include:
- Google Chrome Beta Channel — the beta version
- Google Chrome Dev Channel — the development version
On top of the different Chromium build channels, a number of forks exist with more or less special features; see List of applications#Blink-based.
To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see default applications.
Flash Player plugin
Flash Player is automatically installed when using Google Chrome.
To install it for Chromium, install the package.
Make sure Flash is allowed to run in
Widevine Content Decryption Module plugin
Widevine is Google's Encrypted Media Extensions (EME) Content Decryption Module (CDM). It is used to watch premium video content such as Netflix. It is automatically installed when using Google Chrome.
To install it for Chromium, install the AUR package. Make sure Allow sites to play protected content is checked in
PDF viewer plugin
Chromium and Google Chrome are bundled with the Chromium PDF Viewer plugin. If you don't want to use this plugin, check Open PDFs using a different application in
Chromium uses NSS for certificate management. Certificates can be managed in
Tips and tricks
See the main article: Chromium/Tips and tricks.
Font rendering issues in PDF plugin
To fix the font rendering in some PDFs one has to install the reported on the chromium bug tracker by an Arch user.package, otherwise the substituted font causes text to run into other text. This was
Force 3D acceleration
First follow Hardware video acceleration. Then, to force 3D rendering, enable the flags: "Override software rendering list", "GPU rasterization", "Zero-copy rasterizer" in
chrome://flags. Check if it is working in
chrome://gpu. This may also alleviate tearing issues with the radeon driver.
If "Native GpuMemoryBuffers" under
chrome://gpu mentions software rendering, you additionally need to pass the
--enable-native-gpu-memory-buffers flag, or some optimizations (like the zero-copy rasterizer) won't do anything. This flag isn't available under
chrome://flags - it must be passed in either the chromium-flags.conf file (as noted in Chromium/Tips and tricks#Making flags persistent) or directly on the command line.
There is the possibility that your graphics card has been blacklisted by Chromium. See #Force 3D acceleration.
If you are using Chromium with Bumblebee, WebGL might crash due to GPU sandboxing. In this case, you can disable GPU sandboxing with
optirun chromium --disable-gpu-sandbox.
chrome://gpu/ for debugging information about WebGL support.
Chromium can save incorrect data about your GPU in your user profile (e.g. if you use switch between an Nvidia card using Optimus and Intel, it will show the Nvidia card in
chrome://gpu even when you're not using it or primusrun/optirun). Running using a different user directory, e.g,
chromium --user-data-dir=$(mktemp -d) may solve this issue. For a persistent solution you can reset the GPU information by deleting
Chromium's graphical interface will automatically scale on high-DPI displays. To disable this, use
Password prompt on every start with GNOME Keyring
See GNOME/Keyring#Passwords are not remembered or use Chrome's default internal password storage.
To set it to default and use basic, copy the google-chrome.desktop file from /usr/share/applications into your home folder applications folder:
$ cp /usr/share/applications/google-chrome.desktop ~/.local/share/applications
Open the just copied .desktop file and find each of the lines that begin with Exec and add --password-store=basic.
Exec=/usr/bin/google-chrome-stable --password-store=basic %U
Save the .desktop file. Now when you launch Chrome, you should never be asked for your keyring.
Chromecasts in the network are not discovered
You will need to enable the Media Router Component Extension in
If you see the message
Failed to decrypt token for service AccountId-* in the terminal when you start Chromium, it might try to use the wrong password storage backend. This might happen when you switch between Desktop Environments.