Difference between revisions of "Chromium"

From ArchWiki
Jump to: navigation, search
(Configuration: these topics are covered in other articles, a quick link to them is enough)
m (Flash Player plugin)
 
(210 intermediate revisions by 57 users not shown)
Line 1: Line 1:
 +
[[Category:Web browser]]
 
[[de:Chromium]]
 
[[de:Chromium]]
 
[[es:Chromium]]
 
[[es:Chromium]]
 
[[fr:chromium]]
 
[[fr:chromium]]
 
[[it:Chromium]]
 
[[it:Chromium]]
[[zh-CN:Chromium]]
+
[[ja:Chromium]]
[[Category:Web Browser]]
+
[[ru:Chromium]]
{{Article summary start}}
+
[[zh-hans:Chromium]]
{{Article summary text|General information, installation and troubleshooting for Chromium.}}
+
{{Related articles start}}
{{Article summary heading|Related}}
+
{{Related|Chromium/Tips and tricks}}
{{Article summary wiki|Chromium Tips and Tweaks}}
+
{{Related|Browser plugins}}
{{Article summary wiki|Browser Plugins}}
+
{{Related|Firefox}}
{{Article summary wiki|Firefox}}
+
{{Related|Opera}}
{{Article summary wiki|Opera}}
+
{{Related articles end}}
{{Article summary end}}
+
 
[[Wikipedia:Chromium (web browser)|Chromium]] is an open source graphical web browser from Google, based on the [[Wikipedia:WebKit|WebKit]] rendering engine.
+
[[Wikipedia:Chromium (web browser)|Chromium]] is an open-source graphical web browser from "The Chromium Project", based on the [[Wikipedia:Blink (web engine)|Blink]] rendering engine.
  
 
== Installation ==
 
== Installation ==
  
The open source project, '''Chromium''', can be [[Pacman|installed]] with the package {{Pkg|chromium}}, available in the [[official repositories]].  
+
The open-source project, '''Chromium''', can be [[install]]ed with the {{Pkg|chromium}} package.  
In the [[AUR]] you can also find:
 
* {{AUR|chromium-dev}} - the development version (beware: compiling Chromium takes at least as long as compiling the Linux kernel!)
 
* {{AUR|chromium-browser-bin}} - the binary version of the latest Chromium build
 
  
The modified browser, '''Google Chrome''', bundled with Flash Player and PDF Reader, can be installed with the package {{AUR|google-chrome}}, available in the [[AUR]].
+
Other alternatives include:
In the [[AUR]] you can also find:
 
* {{AUR|google-chrome-beta}} - the beta version
 
* {{AUR|google-chrome-dev}} - the development version
 
  
{{Tip|See these [https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome two] [http://news.softpedia.com/news/Google-Chrome-vs-Chromium-Understanding-Stable-Beta-Dev-Releases-and-Version-No-140060.shtml articles] for an explanation of the differences between Stable/Beta/Dev, as well as Chromium vs. Chrome and the version numbers.}}
+
* {{App|Chromium Beta Channel|the beta version|https://googlechromereleases.blogspot.com/|{{AUR?|chromium-beta}}}}
 +
* {{App|Chromium Dev Channel|the development version|https://googlechromereleases.blogspot.com/|{{AUR|chromium-dev}}}}
 +
* {{App|Chromium snapshot builds|the untested nightly version|https://build.chromium.org/|{{AUR|chromium-snapshot-bin}}}}
 +
* {{App|Chromium with [[VA-API]] support|with a patch to enable VA-API|https://www.chromium.org/|{{AUR|chromium-vaapi}}}}
 +
* {{App|Chromium with GTK+ 3|built with gtk3 instead of gtk2|https://googlechromereleases.blogspot.com/|{{AUR|chromium-gtk3}}}}
  
[http://www.srware.net/en/software_srware_iron.php SRWare Iron], a modified Chromium with altered settings to increase privacy and with built-in ad-blocker, can be installed with the package {{AUR|iron-bin}}, available in the [[AUR]].
+
The derived browser, '''Google Chrome''', bundled with Widevine [[Wikipedia:Encrypted Media Extensions|EME]] (for e.g. Netflix), can be [[install]]ed with the {{AUR|google-chrome}} package.
  
== Configuration ==
+
Other alternatives include:
  
=== Set Chromium as default browser ===
+
* {{App|Google Chrome Beta Channel|the beta version|https://www.google.com/chrome/browser/beta.html|{{AUR|google-chrome-beta}}}}
 +
* {{App|Google Chrome Dev Channel|the development version|https://www.google.com/chrome/browser/|{{AUR|google-chrome-dev}}}}
  
This behaviour is related to [[xdg-open]]: see [[xdg-open#set the default browser]]. For more information about the topic in general, see [[Default Applications]].
+
{{Note|
 
+
* Google Chrome dropped 32 bits support, and only supports 64 bits installation.
=== File associations ===
+
* Support for native client (NaCl) has been dropped in {{pkg|chromium}} version 54, see {{Bug|51511}}. Opening NaCl applications will display this error message: "This plugin is not supported". The {{aur|google-chrome}} package supports NaCl.
 
 
This behaviour is related to [[xdg-open]]: see [[xdg-open#Configuration]]. For more information about the topic in general, see [[Default Applications]].
 
 
 
=== Font rendering ===
 
 
 
Chromium (and Google Chrome) will use the [[Font Configuration|settings]] in {{ic|~/.config/fontconfig/fonts.conf}}. For possibly better rendering you may try the following. Create the file if it does not already exist.
 
 
 
{{hc|~/.config/fontconfig/fonts.conf|
 
<match target&#61;"font">
 
  <edit mode&#61;"assign" name&#61;"autohint"><bool>true</bool></edit>
 
  <edit mode&#61;"assign" name&#61;"hinting"><bool>true</bool></edit>
 
  <edit mode&#61;"assign" name&#61;"hintstyle"><const>hintslight</const></edit>
 
</match>
 
 
}}
 
}}
  
If the fonts are still rendered badly, you can use Xft settings [[X resources|as suggested here]]:
+
See these [https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md two] [http://news.softpedia.com/news/Google-Chrome-vs-Chromium-Understanding-Stable-Beta-Dev-Releases-and-Version-No-140060.shtml articles] for an explanation of the differences between Stable/Beta/Dev, as well as Chromium vs. Chrome and an explanation of the version numbering.
{{hc|~/.Xresources|
 
[...]
 
! Xft settings ---------------------------------------------------------------
 
Xft.dpi:        96
 
Xft.antialias:  true
 
Xft.rgba:      rgb
 
Xft.hinting:    true
 
Xft.hintstyle:  hintslight
 
[...]
 
}}
 
  
Then update the X Resources database using:
+
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]].
  
$ xrdb -merge ~/.Xresources
+
== Configuration ==
 
 
{{Note|These settings will affect any application that uses X Resources for font settings; e.g. [[Rxvt-unicode|rxvt-unicode]].}}
 
 
 
==== Non-Latin characters ====
 
  
Install needed fonts to correctly display Chinese, Japanese, Korean characters. For examples of recommended fonts for various languages see [[Fonts#Font_packages|Font Packages]].
+
=== Default applications ===
  
For the Arch Wiki, one only needs the {{Pkg|ttf-arphic-uming}} package.
+
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 plugin ===
  
==== Adobe (Netscape plugin API) ====
+
{{Note|Chromium no longer supports the Netscape plugin API (NPAPI), so {{pkg|flashplugin}} from the repositories cannot be used.}}
{{Warning|This version will not be updated (except for security updates), and is stuck at version 11.2. It will be completely disabled in January 2014.[http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html]}}
 
The Adobe Flash plugin can be [[Pacman|installed]] with the package {{Pkg|flashplugin}}, available in the official repositories.
 
 
 
==== Adobe (Pepper plugin API) ====
 
  
While the classic Flash plugin will not be updated for Linux, an updated Flash Player is included with Google Chrome. It is compatible with Chromium and Iron.
+
The Flash Player plugin, using the new Pepper plugin API.
  
The easiest way to install '''pepper-flash''' for Chromium is using one of the packages provided in the [[AUR]]:
+
To install it for Chromium or Chrome, [[install]] the {{AUR|pepper-flash}} package.
* {{AUR|chromium-pepper-flash-stable}} for the stable version.
 
* {{AUR|chromium-pepper-flash}} for a development version.
 
  
{{Note|
+
Add the following line (replace the version with the latest one) to {{ic|~/.config/chrome-dev-flags.conf}}.
* If you have still {{pkg|flashplugin}} installed, in order for Chromium to use this new Pepper Flash plugin, please make sure the plugin location from {{ic|/usr/lib/mozilla/plugins/libflashplayer.so}} is disabled and {{ic|/usr/lib/PepperFlash/libpepflashplayer.so}} is enabled in {{ic|chrome://plugins}}.
+
  --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=25.0.0.171
* If you use [http://www.srware.net/en/software_srware_iron.php SRWare Iron], and have still {{pkg|flashplugin}} installed and if the Pepper Flash doesn't show up in the plugins list, then disable {{ic|libflashplayer.so}} and start Iron with:
 
  {{bc|1=$ iron --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.9.900.117}}
 
}}
 
  
=== PDF viewer plugin ===
+
Make sure Flash is allowed to run in {{ic|chrome://settings/content}}.
  
There are multiple ways of enabling PDF support in Chromium that are detailed below.
+
=== Widevine Content Decryption Module plugin ===
  
==== libpdf ====
+
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.
  
'''libpdf''' is Google's own implementation of a PDF renderer included with Google Chrome. It is compatible with Chromium and Iron.
+
To install it for Chromium, [[install]] the {{AUR|chromium-widevine}} package.
  
The easiest way to install '''libpdf''' for Chromium is using one of the packages provided in the [[AUR]]:
+
Make sure ''Allow sites to play protected content'' is checked in {{ic|chrome://settings/content}}.
* {{AUR|chromium-libpdf-stable}} for the stable version.
 
* {{AUR|chromium-libpdf}} for a development version.
 
  
Enable the plugin in {{ic|chrome://plugins}}.
+
=== PDF viewer plugin ===
 
 
{{Note|To install '''libpdf''' for other Chromium packages, edit the PKGBUILD of {{AUR|chromium-libpdf-stable}} to install {{ic|libpdf.so}} into correct path. For example, to install it for {{AUR|chromium-browser-bin}}, replace
 
install -m644 opt/google/chrome/libpdf.so "${pkgdir}''/usr/lib/chromium"''
 
with
 
install -m644 opt/google/chrome/libpdf.so "${pkgdir}''/opt/chromium-browser"''
 
}}
 
  
===== Manual installation =====
+
Chromium and Google Chrome are bundled with the ''Chromium PDF Viewer'' plugin, so installing a third-party plugin is not required.
  
To do it manually, download a Google Chrome release that corresponds to the version of Chromium you use:
+
If you prefer another implementation, check ''Open PDF files in the default PDF viewer application'' at the bottom of {{ic|chrome://settings/content}}, and install one of the alternatives from [[Browser plugins#PDF viewer]].
 
 
$ curl -O https://dl-ssl.google.com/linux/direct/google-chrome-stable_current_i386.deb
 
$ curl -O https://dl-ssl.google.com/linux/direct/google-chrome-unstable_current_i386.deb
 
$ curl -O https://dl-ssl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
 
$ curl -O https://dl-ssl.google.com/linux/direct/google-chrome-unstable_current_amd64.deb
 
 
 
Extract the deb file with:
 
$ ar vx ''deb-file''
 
 
 
Extract LZMA the archive with:
 
$ tar -xJf ''lzma-file''
 
 
 
Move {{ic|libpdf.so}} from {{ic|opt/google/chrome/}} to the appropriate directory as stated above. A change of its file permissions and ownership may be necessary (the permission of {{ic|libpdf.so}} should be 755).
 
 
 
To verify that the installation went correctly: start Chromium, open {{ic|chrome://plugins/}} and check  if "Chrome PDF Viewer" is available (it may need to be enabled).
 
 
 
{{Note|As a new version of Chromium will not update {{ic|libpdf.so}}, it may become incompatible. Thus and with respect to possible security fixes it is advisable to update both at the same time.}}
 
 
 
==== Using mozplugger ====
 
 
 
{{Box||See the main article: [[Browser Plugins#MozPlugger]]|#E5E5FF|#FCFCFC}}
 
 
 
==== Using the KParts plugin ====
 
 
 
{{Box||See the main article: [[Browser Plugins#kpartsplugin]]|#E5E5FF|#FCFCFC}}
 
  
 
=== Certificates ===
 
=== Certificates ===
  
Chromium uses [[Nss|NSS]] for the certificate management. Certificates can be managed in {{ic|Settings}} → {{ic|Show advanced settings...}} → {{ic|Manage Certificates...}}.
+
Chromium uses [[Network Security Services|NSS]] for certificate management. Certificates can be managed in {{ic|chrome://settings/certificates}}.
  
 
== Tips and tricks ==
 
== Tips and tricks ==
  
{{Box||See the main article: [[Chromium Tips and Tweaks]]|#E5E5FF|#FCFCFC}}
+
See the main article: [[Chromium/Tips and tricks]].
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
=== Proxy settings ===
+
=== Constant freezes under KDE ===
 
 
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 {{ic|--proxy-pac-url}} and {{ic|--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:
+
[[Uninstall]] {{pkg|libcanberra-pulse}}. See: [https://bbs.archlinux.org/viewtopic.php?pid=1228558 BBS#1228558].
{{hc|$ chromium|
 
[2630:2630:485325611:FATAL:chrome/browser/browser_main.cc(755)] Check failed: profile.  
 
Cannot get default profile. Trace/breakpoint trap
 
}}
 
  
You have to set the correct owner of the directory {{ic|~/.config/chromium}} as following:
+
=== Fonts ===
# chown -R ''yourusername'':''yourusergroup'' ~/.config/chromium
 
  
=== WebGL ===
+
{{Note|Chromium does not fully integrate with fontconfig/GTK/Pango/X/etc. due to its sandbox. For more information, see the [https://dev.chromium.org/developers/linux-technical-faq Linux Technical FAQ].}}
  
Sometimes, Chromium will disable WebGL with certain graphics card configurations. This can generally be remedied by typing {{ic|about:flags}} into the URL bar and enabling the WebGL flag. You may also enable WebGL by passing the command line flag {{ic|--enable-webgl}} to Chromium in the terminal.
+
==== Font rendering issues in PDF plugin ====
  
There is also the possibility that your graphics card has been blacklisted by Chromium. To override this use the {{ic|--ignore-gpu-blacklist}} flag or go to {{ic|about:flags}} and enable {{ic|Override software rendering list}}.
+
To fix the font rendering in some PDFs one has to install the {{Pkg|ttf-liberation}} package, otherwise the substituted font causes text to run into other text. This was [https://code.google.com/p/chromium/issues/detail?id=369991 reported on the chromium bug tracker] by an Arch user.
  
=== Google Play and Flash ===
+
=== Force 3D acceleration ===
  
{{Out of date|HAL is no longer used in Arch.}}
+
{{Warning|Disabling the rendering blacklist may cause unstable behaviour, including crashes of the host. See the bug reports in {{ic|chrome://gpu}}.}}
  
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.
+
First follow [[Hardware video acceleration]]. Then, to force 3D rendering, ''enable'' the flags: "Override software rendering list", "GPU rasterization", "Zero-copy rasterizer" in {{ic|chrome://flags}}. Check if it is working in {{ic|chrome://gpu}}. This may also alleviate tearing issues with the [[radeon]] driver.
  
{{Note|{{AUR|chromium-pepper-flash}} does not work with this method. The user must ensure they are using {{Pkg|flashplugin}}.}}
+
If "Native GpuMemoryBuffers" under {{ic|chrome://gpu}} mentions software rendering, you additionally need to pass the {{ic|--enable-native-gpu-memory-buffers}} flag, or some optimizations (like the zero-copy rasterizer) won't do anything. This flag isn't available under {{ic|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.
  
As per [http://isenmann.blogspot.gr/2012/08/watching-movies-from-google-play-with.html "Watching movies from Google Play on Arch Linux"]; install {{AUR|hal}} and {{AUR|hal-info}}. Then remove any previous cache files for Flash:
+
=== WebGL ===
$ rm -rf ~/.adobe/Flash_Player/*
+
{{Warning|[[Catalyst]] does not support the {{ic|GL_ARB_robustness}} extension. When using this driver, it is possible that a malicious site could use WebGL to perform a DoS attack on your graphic card.}}
  
Start the HAL daemon and one will be able to watch Google Play Movie content.
+
There is the possibility that your graphics card has been blacklisted by Chromium. See [[#Force 3D acceleration]].
{{bc|<nowiki>
 
# systemctl start hal
 
</nowiki>}}
 
  
Alternately one can just save the following Bash script below and run it before they want to watch Google Play Movie content.
+
If you are using Chromium with [[Bumblebee]], WebGL might crash due to GPU sandboxing. In this case, you can disable GPU sandboxing with {{ic|optirun chromium --disable-gpu-sandbox}}.
{{bc|<nowiki>
 
#!/bin/bash
 
  
## written by Mark Lee <bluerider>
+
Visit {{ic|chrome://gpu/}} for debugging information about WebGL support.
## using information from <https://wiki.archlinux.org/index.php/Chromium#Google_Play_.26_Flash>
 
  
## Start and stop HAL service on command for Google Play Movie service
+
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 {{ic|chrome://gpu}} even when you're not using it or primusrun/optirun). Running using a different user directory, e.g, {{ic|1=chromium --user-data-dir=$(mktemp -d)}} may solve this issue. For a persistent solution you can reset the GPU information by deleting {{ic|~/.config/chromium/Local\ State}}.
  
function main () {  ## run the main insertion function
+
=== Distorted GUI ===
clear-cache;  ## remove adobe cache
 
start-hal;  ## start the hal daemon
 
read -p "Press 'enter' to stop hal";  ## pause the command line with a read line
 
stop-hal;  ## stop the hal daemon
 
}
 
  
function clear-cache () {  ## remove adobe cache
+
Chromium's graphical interface may look unsightly, distorted and zoomed in on high-DPI displays. To disable any attempts to scale display according to device DPI, use {{ic|1=--force-device-scale-factor=1}}.
cd ~/.adobe/Flash_Player;  ## go to Flash player user directory
 
rm -rf NativeCache AssetCache APSPrivateData2;  ## remove cache
 
}
 
  
function start-hal () {  ## start the hal daemon
+
=== Disable keyring password prompt ===
sudo systemctl start hal && ( ## systemd : start hal daemon
 
echo "Started HAL service..."
 
) || (
 
echo "Failed to start HAL service!"
 
)
 
}
 
  
function stop-hal () { ## stop the hal daemon
+
{{Accuracy|1=Is this a reference to a chrome 53 bug? [https://bbs.archlinux.org/viewtopic.php?id=216736] If so, it's fixed in 53.0.2785.101-1}}
sudo systemctl stop hal && (  ## systemd : stop HAL daemon
 
echo "Stopped HAL service..."
 
) || (
 
echo "Failed to stop HAL service!"
 
)
 
}
 
  
main;  ## run the main insertion function
+
See [[GNOME/Keyring#Passwords are not remembered]]. You may also need to edit the Chromium command line to append {{ic|1=--password-store=gnome}}.
</nowiki>}}
 
  
=== Force 3D acceleration in Pepper Flash Player and i.g. the browser with radeon driver ===
+
=== Chromecasts in the network are not discovered ===
  
To force 3D rendering  there is an option  "Override software rendering list" in {{ic|chrome://flags}}, also you would have to export video acceleration variables, see [[ATI#Enabling_video_acceleration]]. You could check if it is working in  {{ic|chrome://gpu}}.
+
You will need to enable the Media Router Component Extension in {{ic|chrome://flags/#load-media-router-component-extension}}.
  
 
== See also ==
 
== See also ==
  
* [http://www.chromium.org/Home Chromium homepage]
+
* [https://www.chromium.org/ Chromium homepage]
* [http://googlechromereleases.blogspot.com Google Chrome release notes]
+
* [https://googlechromereleases.blogspot.com Google Chrome release notes]
 
* [https://chrome.google.com/webstore/category/home Chrome web store]
 
* [https://chrome.google.com/webstore/category/home Chrome web store]
* [[Wikipedia: Chromium_(web_browser)#Differences_from_Google_Chrome|Differences between Chromium and Google Chrome]]
+
* [[Wikipedia:Chromium (web browser)#Differences from Google Chrome|Differences between Chromium and Google Chrome]]
 
* [http://peter.sh/experiments/chromium-command-line-switches/ List of Chromium command-line switches]
 
* [http://peter.sh/experiments/chromium-command-line-switches/ List of Chromium command-line switches]

Latest revision as of 04:06, 22 May 2017

Chromium is an open-source graphical web browser from "The Chromium Project", based on the Blink rendering engine.

Installation

The open-source project, Chromium, can be installed with the chromium package.

Other alternatives include:

  • Chromium Beta Channel — the beta version
https://googlechromereleases.blogspot.com/ || not packaged? search in AUR
  • Chromium Dev Channel — the development version
https://googlechromereleases.blogspot.com/ || chromium-devAUR
  • Chromium snapshot builds — the untested nightly version
https://build.chromium.org/ || chromium-snapshot-binAUR
  • Chromium with VA-API support — with a patch to enable VA-API
https://www.chromium.org/ || chromium-vaapiAUR
  • Chromium with GTK+ 3 — built with gtk3 instead of gtk2
https://googlechromereleases.blogspot.com/ || chromium-gtk3AUR

The derived browser, Google Chrome, bundled with Widevine EME (for e.g. Netflix), can be installed with the google-chromeAUR package.

Other alternatives include:

  • Google Chrome Beta Channel — the beta version
https://www.google.com/chrome/browser/beta.html || google-chrome-betaAUR
  • Google Chrome Dev Channel — the development version
https://www.google.com/chrome/browser/ || google-chrome-devAUR
Note:
  • Google Chrome dropped 32 bits support, and only supports 64 bits installation.
  • Support for native client (NaCl) has been dropped in chromium version 54, see FS#51511. Opening NaCl applications will display this error message: "This plugin is not supported". The google-chromeAUR package supports NaCl.

See these two articles for an explanation of the differences between Stable/Beta/Dev, as well as Chromium vs. Chrome and an explanation of the version numbering.

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.

Configuration

Default applications

To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see default applications.

Flash Player plugin

Note: Chromium no longer supports the Netscape plugin API (NPAPI), so flashplugin from the repositories cannot be used.

The Flash Player plugin, using the new Pepper plugin API.

To install it for Chromium or Chrome, install the pepper-flashAUR package.

Add the following line (replace the version with the latest one) to ~/.config/chrome-dev-flags.conf.

--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=25.0.0.171

Make sure Flash is allowed to run in chrome://settings/content.

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 chromium-widevineAUR package.

Make sure Allow sites to play protected content is checked in chrome://settings/content.

PDF viewer plugin

Chromium and Google Chrome are bundled with the Chromium PDF Viewer plugin, so installing a third-party plugin is not required.

If you prefer another implementation, check Open PDF files in the default PDF viewer application at the bottom of chrome://settings/content, and install one of the alternatives from Browser plugins#PDF viewer.

Certificates

Chromium uses NSS for certificate management. Certificates can be managed in chrome://settings/certificates.

Tips and tricks

See the main article: Chromium/Tips and tricks.

Troubleshooting

Constant freezes under KDE

Uninstall libcanberra-pulse. See: BBS#1228558.

Fonts

Note: Chromium does not fully integrate with fontconfig/GTK/Pango/X/etc. due to its sandbox. For more information, see the Linux Technical FAQ.

Font rendering issues in PDF plugin

To fix the font rendering in some PDFs one has to install the ttf-liberation package, otherwise the substituted font causes text to run into other text. This was reported on the chromium bug tracker by an Arch user.

Force 3D acceleration

Warning: Disabling the rendering blacklist may cause unstable behaviour, including crashes of the host. See the bug reports in chrome://gpu.

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.

WebGL

Warning: Catalyst does not support the GL_ARB_robustness extension. When using this driver, it is possible that a malicious site could use WebGL to perform a DoS attack on your graphic card.

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.

Visit 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 ~/.config/chromium/Local\ State.

Distorted GUI

Chromium's graphical interface may look unsightly, distorted and zoomed in on high-DPI displays. To disable any attempts to scale display according to device DPI, use --force-device-scale-factor=1.

Disable keyring password prompt

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: Is this a reference to a chrome 53 bug? [1] If so, it's fixed in 53.0.2785.101-1 (Discuss in Talk:Chromium#)

See GNOME/Keyring#Passwords are not remembered. You may also need to edit the Chromium command line to append --password-store=gnome.

Chromecasts in the network are not discovered

You will need to enable the Media Router Component Extension in chrome://flags/#load-media-router-component-extension.

See also