Difference between revisions of "Chromium"

From ArchWiki
Jump to: navigation, search
m (sudo is not needed)
(Troubleshooting: there no longer is an --enable-webgl flag (checked in chrome://flags and http://peter.sh/experiments/chromium-command-line-switches/))
 
(208 intermediate revisions by 54 users not shown)
Line 1: Line 1:
 +
[[Category:Web browser]]
 +
[[de:Chromium]]
 
[[es:Chromium]]
 
[[es:Chromium]]
 
[[fr:chromium]]
 
[[fr:chromium]]
 
[[it:Chromium]]
 
[[it:Chromium]]
 +
[[ja:Chromium]]
 +
[[ru:Chromium]]
 
[[zh-CN:Chromium]]
 
[[zh-CN:Chromium]]
[[Category:Web Browser]]
+
{{Related articles start}}
{{Article summary start}}
+
{{Related|Chromium/Tips and tricks}}
{{Article summary text|General information, installation and troubleshooting for Chromium.}}
+
{{Related|Browser plugins}}
{{Article summary heading|Related}}
+
{{Related|Firefox}}
{{Article summary wiki|Chromium Tips and Tweaks}}
+
{{Related|Opera}}
{{Article summary wiki|Browser Plugins}}
+
{{Related articles end}}
{{Article summary wiki|Firefox}}
+
 
{{Article summary wiki|Opera}}
+
[[Wikipedia:Chromium (web browser)|Chromium]] is an open-source graphical web browser from "The Chromium Project", based on the [[Wikipedia:Blink (layout engine)|Blink]] rendering engine.
{{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.
+
  
 
== Installation ==
 
== Installation ==
The open source project, '''Chromium''', can be [[Pacman|installed]] with the package {{Pkg|chromium}}, available in the [[official repositories]].
 
In the [[AUR]] you can also find:
 
* {{AUR|chromium-dev}} - the development version
 
* {{AUR|chromium-browser-bin}} - the binary version of the latest Chromium build
 
* {{AUR|iron-bin}} - the binary version of SRWare Iron: modified Chromium with altered settings to increase privacy and with built-in ad-blocker
 
  
{{Note|Compiling {{AUR|chromium-dev}} takes at least as long as compiling the Linux kernel.}}
+
The open-source project, '''Chromium''', can be [[install]]ed with the {{Pkg|chromium}} package.  
  
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
+
  
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}}}}
  
== Configuration ==
+
The derived browser, '''Google Chrome''', bundled with Flash Player and Widevine [[Wikipedia:Encrypted Media Extensions|EME]] (for e.g. Netflix), can be [[install]]ed with the {{AUR|google-chrome}} package.
  
=== File associations ===
+
Other alternatives include:
Unlike [[Firefox]], Chromium does not maintain its own database of mimetype-to-application associations. Instead, it relies on [[Xdg-open|xdg-open]] to open files and other mime types and URI schemes, for example, [[Wikipedia:Magnet URI scheme|magnet links]]. There are exceptions to this rule though, for example in the case of ''mailto'' URIs, Chromium calls {{ic|xdg-email}}, which is also part of {{Pkg|xdg-utils}} package.
+
  
Refer to [[Xdg-open|xdg-open]], [[Default Applications|default applications]] or [[Environment Variables|environment variables]] on how to set up default file associations.
+
* {{App|Google Chrome Beta Channel|the beta version|https://www.google.com/chrome|{{AUR|google-chrome-beta}}}}
 +
* {{App|Google Chrome Dev Channel|the development version|https://www.google.com/chrome|{{AUR|google-chrome-dev}}}}
  
==== Default browser ====
+
{{Note|Google Chrome dropped 32 bits support, and only supports 64 bits installation}}
  
{{Merge|Xdg-open|cover the topic in one place, not on every page of every browser}}
+
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.
  
The simplest way to make Chromium the default browser is to set variable {{Ic|<nowiki>$BROWSER=chromium</nowiki>}} in {{ic|~/.profile}}
+
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]].
if [ -n "$DISPLAY" ]; then
+
      BROWSER=chromium
+
fi
+
  
To test if this was applied successfully, try to open an URL with {{ic|xdg-open}} as follows:
+
== Configuration ==
$ xdg-open http://google.com/
+
If everything went well, either a new tab inside Chromium, or a new window would open and display the Google homepage, depending on your settings.
+
 
+
Another option, when using {{AUR|mimeo}}, is to associate "http://" links with Chromium:
+
{{hc|~/.config/mimeo.conf|<nowiki>
+
/usr/bin/chromium
+
  ^http://
+
</nowiki>}}
+
 
+
If all of that still does not get it working, you can try adding the following to the {{ic|[Added Associations]}} list in  {{ic|~/.local/share/applications/mimeapps.list}}:
+
x-scheme-handler/http=chromium.desktop
+
 
+
If even that didn't work, try this:
+
{{bc|$ xdg-mime default chromium.desktop x-scheme-handler/http
+
$ xdg-mime default chromium.desktop x-scheme-handler/https}}
+
 
+
For more info, see [[Xdg-open]].
+
 
+
=== Font Rendering ===
+
Chromium is now supposed to use the settings in {{ic|~/.fonts.conf}}, though you may have to edit it manually (see [[Font_Configuration#Basic_settings|Font Configuration]]).
+
If your fonts setting are stored in another place, create {{ic|~/.fonts.conf}} and add these lines:
+
{{hc|~/.fonts.conf|
+
<match target&#61;"font">
+
    <edit name&#61;"autohint" mode&#61;"assign">
+
      <bool>true</bool>
+
    </edit>
+
    <edit name&#61;"hinting" mode&#61;"assign">
+
      <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]]. Create {{ic|~/.Xresources}} if it does not exist and add in:
+
{{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:
+
 
+
{{bc|xrdb -merge ~/.Xresources}}
+
 
+
{{Note|These settings will affect any application that uses X Resources for font settings; one example is [[Rxvt-unicode|rxvt-unicode]].}}
+
  
==== Non-Latin characters ====
+
=== Default applications ===
Install needed fonts to correctly display Chinese, Japanese, Korean characters. For examples of recommended fonts for various languages see [[Fonts#Font_packages|Font Packages]].
+
  
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.}}
{{Note|This version will not be updated (except for security updates), and is stuck at version 11.2.}}
+
The Adobe Flash plugin can be [[Pacman|installed]] with the package {{Pkg|flashplugin}}, available in the official repositories.  
+
  
==== Adobe (Pepper Plugin API) ====
+
''Pepper Flash'' is the Flash Player plugin, using the new Pepper plugin API. It is included with Google Chrome. To install it for Chromium, [[install]] it the {{AUR|pepper-flash}} package.
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 easiest way to install '''pepper-flash''' for Chromium is using one of the packages provided in the [[AUR]]:
+
Make sure the plugin is enabled in {{ic|chrome://plugins}} and restart Chromium via its menu.
* {{AUR|chromium-pepper-flash-stable}} for the stable version.
+
* {{AUR|chromium-pepper-flash}} for a development version.
+
  
Enable the Flash Player plugin with location {{ic|/usr/lib/PepperFlash/libpepflashplayer.so}} in {{ic|chrome://plugins}} and disable the plugin with location {{ic|/usr/lib/mozilla/plugins/libflashplayer.so}}.
+
=== Widevine Content Decryption Module plugin ===
  
{{Note|1=If Pepper Flash doesn't show up in the plugins list (as is the case for Iron), then disable {{ic|libflashplayer.so}} and start with
+
Widevine is Google's Encrypted Media Extensions (EME) Content Decryption Module (CDM). It is used to watch premium video content such as Netflix. It comes bundled with Chrome.
{{bc|1=iron --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.7.700.169}}
+
}}
+
  
=== PDF Viewer plugin ===
+
To install the Widevine CDM for Chromium, install the {{AUR|chromium-widevine}} package.
There are multiple ways of enabling PDF support in Chromium that are detailed below.
+
  
==== libpdf ====
+
Make sure the plugin is enabled in {{ic|chrome://plugins}}.
'''libpdf''' is Google's own implementation of a PDF renderer included with Google Chrome. It is compatible with Chromium and Iron.
+
  
The easiest way to install '''libpdf''' for Chromium is using one of the packages provided in the [[AUR]]:
+
=== PDF viewer plugin ===
* {{AUR|chromium-libpdf-stable}} for the stable version.
+
* {{AUR|chromium-libpdf}} for a development version.
+
  
Enable the plugin in {{ic|chrome://plugins}}.
+
Chromium and Google Chrome are bundled with the ''Chromium PDF Viewer'' plugin, so installing a third-party plugin is not required.
  
{{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
+
If you prefer another implementation, disable the ''Chromium PDF Viewer'' plugin in {{ic|chrome://plugins}}, and install one of the following alternatives:
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 =====
+
==== PDF.js ====
To do it manually, download a Google Chrome release that corresponds to the version of Chromium you use:
+
  
$ wget https://dl-ssl.google.com/linux/direct/google-chrome-stable_current_i386.deb
+
See the main article: [[Browser plugins#PDF.js]]
$ wget https://dl-ssl.google.com/linux/direct/google-chrome-unstable_current_i386.deb
+
$ wget https://dl-ssl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
+
$ wget https://dl-ssl.google.com/linux/direct/google-chrome-unstable_current_amd64.deb
+
  
Extract the deb file with
+
=== Certificates ===
$ ar vx <deb-file>
+
  
Extract LZMA archive with
+
Chromium uses [[Network Security Services|NSS]] for certificate management. Certificates can be managed in {{ic|Settings}} → {{ic|Show advanced settings...}} → {{ic|Manage Certificates...}}.
$ 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).
+
== Tips and tricks ==
  
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).
+
See the main article: [[Chromium/Tips and tricks]].
  
{{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.}}
+
== Troubleshooting ==
  
==== Using mozplugger ====
+
=== Constant freezes under KDE ===
{{Box||See the main article: [[Browser Plugins#MozPlugger]]|#E5E5FF|#FCFCFC}}
+
  
==== Using the KParts plugin ====
+
[[Uninstall]] {{pkg|libcanberra-pulse}}. See: [https://bbs.archlinux.org/viewtopic.php?pid=1228558 BBS#1228558].
{{Box||See the main article: [[Browser Plugins#kpartsplugin]]|#E5E5FF|#FCFCFC}}
+
  
=== Certificates ===
+
=== Fonts ===
Chromium uses [[Nss|NSS]] for the certificate management. Certificates can be managed (including added) by going to ''Settings'', clicking the  ''Show advanced settings..'' link and then ''Manage Certificates''.
+
  
== Tips and Tricks ==
+
{{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].}}
{{Box||See the main article: [[Chromium Tips and Tweaks]]|#E5E5FF|#FCFCFC}}
+
  
== Troubleshooting ==
+
==== Font rendering issues in PDF plugin ====
  
=== Proxy Settings ===
+
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.
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 ===
+
=== Force 3D acceleration ===
  
If you cannot get your default profile when you try to run Chromium and get a similar error instead:
+
{{Warning|Disabling the rendering list may cause unstable behaviour, including crashes of the host. See the bug reports in {{ic|chrome://gpu}}.}}
{{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:
+
First follow [[Hardware video acceleration]]. Then, to force 3D rendering, ''enable'' the flag "Override software rendering list" in {{ic|chrome://flags}}. Check if it is working in {{ic|chrome://gpu}}. This may also alleviate tearing issues with the [[radeon]] driver.
# chown -R yourusername:yourusergroup ~/.config/chromium
+
  
 
=== WebGL ===
 
=== WebGL ===
  
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.
+
{{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.}}
 
+
There is also the possibility that your graphics card has been blacklisted by Chromium. To override this, pass the flag {{ic|--ignore-gpu-blacklist}} when starting Chromium, alternatively, go to {{ic|about:flags}} and enable ''Override software rendering list''.
+
 
+
=== Pulseaudio & PA-Alsa-Bridge & 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 [http://code.google.com/p/chromium/issues/detail?id=128870] for the bugreport.
+
 
+
A possible workaround is to use {{ic|pasuspender}} to suspend Pulseaudio and force Chrome to use Alsa directly.
+
 
+
First, create an {{ic|~/.asoundrc}} file to default Alsa to your real hardware instead of Pulseaudio. See [[Alsa]] and [http://alsa.opensrc.org/FAQ026] for more information. Exemplary {{ic|~/.asoundrc}}:
+
 
+
{{hc|~/.asoundrc|
+
pcm. !default {
+
    type hw
+
    card 0
+
    device 0
+
}
+
}}
+
 
+
Then use {{ic|pasuspender}} to suspend Pulseaudio and force Chrome to use Alsa which now uses your real hardware.
+
 
+
{{bc|
+
pasuspender -- google-chrome
+
}}
+
 
+
The problem might be related to the tsched=0 option in Pulseaudio. See [[Pulseaudio#Glitches, skips or crackling]] and comment #27 in [http://code.google.com/p/chromium/issues/detail?id=128870#c27].
+
 
+
=== Google Play & 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.
+
 
+
{{note|{{AUR|chromium-pepper-flash}} does not work with this method. The user must ensure they are using {{Pkg|flashplugin}}.}}
+
 
+
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 run the following Bash code:
+
{{bc|<nowiki>
+
cd ~/.adobe/Flash_Player;                      ## enter the Adobe Flash Player directory
+
rm -rf NativeCache AssetCache APSPrivateData2;  ## remove cache
+
</nowiki>}}
+
 
+
Start the HAL daemon and one will be able to watch Google Play Movie content.
+
{{bc|<nowiki>
+
# systemctl start hal.service
+
</nowiki>}}
+
  
Alternately one can just save the following Bash script below and run it before they want 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>
+
#!/bin/bash
+
  
## written by Mark Lee <bluerider>
+
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}}.
## 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
+
If none of the above solves your problem, you may be able to visit {{ic|chrome://gpu/}} for additional debugging info.
  
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.service && ( ## 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.service && (  ## 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 ===
+
== See also ==
  
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 https://wiki.archlinux.org/index.php/ATI#Enabling_video_acceleration; you could check if it is working in  chrome://gpu
+
* [https://www.chromium.org/ Chromium homepage]
== See Also ==
+
* [https://googlechromereleases.blogspot.com Google Chrome release notes]
* [http://www.chromium.org/Home Chromium Homepage]
+
* [https://chrome.google.com/webstore/category/home Chrome web store]
* [http://googlechromereleases.blogspot.com Google Chrome Release Notes]
+
* [[Wikipedia:Chromium (web browser)#Differences from Google Chrome|Differences between Chromium and Google Chrome]]
* [https://chrome.google.com/webstore/category/home Chrome Web Store]
+
* [[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 12:49, 11 September 2016

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

The derived browser, Google Chrome, bundled with Flash Player and 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 || google-chrome-betaAUR
  • Google Chrome Dev Channel — the development version
https://www.google.com/chrome || google-chrome-devAUR
Note: Google Chrome dropped 32 bits support, and only supports 64 bits installation

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.

Pepper Flash is the Flash Player plugin, using the new Pepper plugin API. It is included with Google Chrome. To install it for Chromium, install it the pepper-flashAUR package.

Make sure the plugin is enabled in chrome://plugins and restart Chromium via its menu.

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 comes bundled with Chrome.

To install the Widevine CDM for Chromium, install the chromium-widevineAUR package.

Make sure the plugin is enabled in chrome://plugins.

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, disable the Chromium PDF Viewer plugin in chrome://plugins, and install one of the following alternatives:

PDF.js

See the main article: Browser plugins#PDF.js

Certificates

Chromium uses NSS for certificate management. Certificates can be managed in SettingsShow advanced settings...Manage 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 list 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 flag "Override software rendering list" in chrome://flags. Check if it is working in chrome://gpu. This may also alleviate tearing issues with the radeon driver.

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.

If none of the above solves your problem, you may be able to visit chrome://gpu/ for additional debugging info.

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.

See also