Difference between revisions of "Chromium"

From ArchWiki
Jump to: navigation, search
(Non-Latin characters: added bit for arch wiki niceness)
m (Tips and tricks: style)
 
(202 intermediate revisions by 49 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 Google, 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 ==
Chromium can be [[Pacman|installed]] with the package {{Pkg|chromium}}, available in the [[official repositories]].
 
  
In the [[AUR]] you can also find:
+
The open-source project, '''Chromium''', can be [[install]]ed with the {{Pkg|chromium}} package.
* {{AUR|chromium-dev}} - a development version of the Chromium browser.
+
You can also find:
* {{AUR|chromium-update}} - an update. script for Chromium nighly builds, pre-compiled on the Chromium buildbot server.
+
* {{AUR|chromium-dev}} - the development version
* {{AUR|chromium-browser-bin}} - a binary version of the latest Chromium build.
+
* {{AUR|chromium-continuous-bin}}{{Broken package link|{{aur-mirror|chromium-continuous-bin}}}} - the automatically tested nightly version
* {{AUR|iron-bin}} - a binary version of Chromium without Google's 'tracking features'
+
* {{AUR|chromium-snapshot-bin}} - the untested nightly version
  
{{Note|Compiling {{AUR|chromium-dev}} takes at least as long as compiling the Linux kernel.}}
+
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.
 +
You can also find:
 +
* {{AUR|google-chrome-beta}} - the beta version
 +
* {{AUR|google-chrome-dev}} - the development version
  
Various versions of the modified Google Chrome browser can be found in the [[AUR]]:
+
{{Note|Google Chrome revoked 32 bits support, and only supports 64 bits installation}}
* {{AUR|google-chrome}}
+
* {{AUR|google-chrome-beta}}
+
* {{AUR|google-chrome-dev}}
+
  
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.
+
{{Tip|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.}}
  
== Configuration ==
+
=== Inox ===
  
=== File associations ===
+
Inox is a privacy-focused patchset which disables Google services, proprietary features, prevents "calling home" and unhides all extensions. Flags are stored in {{ic|inox-flags.conf}}. See [https://github.com/gcarq/inox-patchset this GitHub project] for details. Otherwise, instructions regarding Chromium apply equally.
  
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, for example, [[Wikipedia:Magnet URI scheme|magnet links]].
+
* {{AUR|inox-bin}} - prebuilt binaries.
 +
* {{AUR|inox}} - Allows disabling additional features in PKGBUILD. Takes a '''long''' time to build, regardless of your CPU.
  
There are exceptions to this rule though. In the case of ''mailto'' URIs, Chromium calls out to {{ic|xdg-email}} which is similar to {{ic|xdg-open}}. Other protocol handlers may have equivalent scripts so check {{ic|/usr/bin/xdg*}}.
+
== Configuration ==
  
The behaviour of {{ic|xdg-*}} tools is managed automatically in environments such as [[GNOME]], [[KDE]], [[Xfce]] or [[LXDE]], but does not work in others. Usually this behaviour can be fixed by tricking them into thinking that they are operating in one of the supported desktop environments. Depending on your environment one may work and another will not so trying each is recommended. You can set the desktop environment with the following variable:
+
=== Set Chromium as default browser ===
export DE=INSERT_DE_HERE
+
  
where the recognised desktop environments are: '''gnome''', '''kde''', '''xfce''' and '''lxde'''. For the variable to be always set, put it somewhere like {{ic|~/.xinitrc}} or {{ic|~/.bashrc}}.
+
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]].
  
An alternative is to edit the {{ic|xdg-open}} or {{ic|xdg-email}} scripts and '''hard-code''' a useful DE. At the bottom of the file you will see something like this:
+
=== File associations ===
{{hc|/usr/bin/xdg-open|<nowiki>
+
detectDE
+
  
if [ x"$DE" = x"" ]; then
+
This behaviour is related to [[xdg-open]]: see [[xdg-open#Configuration]]. For more information about the topic in general, see [[Default applications]].
    DE=generic
+
fi
+
  
DEBUG 2 "Selected DE $DE"
+
=== Flash Player plugin ===
  
# if BROWSER variable is not set, check some well known browsers instead
+
{{Note|Chromium no longer supports the Netscape plugin API (NPAPI), so {{pkg|flashplugin}} from the repositories cannot be used.}}
if [ x"$BROWSER" = x"" ]; then
+
    BROWSER=links2:elinks:links:lynx:w3m
+
    if [ -n "$DISPLAY" ]; then
+
        BROWSER=x-www-browser:firefox:seamonkey:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER
+
    fi
+
fi
+
  
case "$DE" in
+
''Pepper Flash'' is the Flash Player plugin, using the new Pepper plugin API. It is co-developed by Google and Adobe, and distributed bundled with Google Chrome.
    kde)
+
    open_kde "$url"
+
    ;;
+
  
    gnome*)
+
To install Pepper Flash for Chromium, install the {{AUR|chromium-pepper-flash}} package. If you want the development version, install the {{AUR|chromium-pepper-flash-dev}} package instead.
    open_gnome "$url"
+
    ;;
+
  
    mate)
+
Make sure the plugin is enabled in {{ic|chrome://plugins}} and restart chromium via its menu.
    open_mate "$url"
+
    ;;
+
  
    xfce)
+
=== Widevine Content Decryption Module plugin ===
    open_xfce "$url"
+
    ;;
+
  
    lxde)
+
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.
    open_lxde "$url"
+
    ;;
+
  
    generic)
+
To install the Widevine CDM for Chromium, install the {{AUR|chromium-widevine}} package.
    open_generic "$url"
+
    ;;
+
  
    *)
+
Make sure the plugin is enabled in {{ic|chrome://plugins}}.
    exit_failure_operation_impossible "no method available for opening '$url'"
+
    ;;
+
esac</nowiki>
+
}}
+
  
change the third line: {{ic|DE&#61;generic}} to one of the supported desktop environments (e.g. {{ic|DE&#61;gnome}}).
+
=== PDF viewer plugin ===
  
{{Note|These changes are lost when any of the utilities are upgraded.}}
+
Chromium and Google Chrome are bundled with the ''Chromium PDF Viewer'' plugin, so installing a third-party plugin is not required.
  
An approach which is less useful is to place the required application in the default browser list:
+
If you prefer another implementation, disable the ''Chromium PDF Viewer'' plugin in {{ic|chrome://plugins}}, and install one of the following alternatives:
  
    BROWSER=links2:links:lynx:w3m
+
==== PDF.js ====
    if [ -n "$DISPLAY" ]; then
+
        BROWSER=firefox:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER
+
    fi
+
  
{{ic|xdg-open}} and {{ic|xdg-email}} fall back to this list of browsers and will use the first that they find to attempt to open the URI. You could add the name of the application to the beginning of the list. However there is no guarantee that the application will be called correctly to meet your needs, e.g. your mail client will open but it will not correctly receive the ''mailto'' address. Also it will only work for one application.
+
See the main article: [[Browser plugins#PDF.js]]
  
A fourth option is to make a softlink from your preferred application to one of the names on the browser list. This approach has the same problems as the previous work around. For more discussion on these ideas see [https://bbs.archlinux.org/viewtopic.php?id=81282&p=1 this forum thread].
+
=== Certificates ===
  
=== Font Rendering ===
+
Chromium uses [[Network Security Services|NSS]] for certificate management. Certificates can be managed in {{ic|Settings}} {{ic|Show advanced settings...}} {{ic|Manage Certificates...}}.
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:
+
== Tips and tricks ==
  
{{bc|xrdb -merge ~/.Xresources}}
+
See the main article: [[Chromium/Tips and tricks]].
  
{{Note|These settings will affect any application that uses X Resources for font settings; one example is [[Rxvt-unicode|rxvt-unicode]].}}
+
== Troubleshooting ==
  
==== Non-Latin characters ====
+
=== Constant freezes under KDE ===
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.
+
[[Uninstall]] {{pkg|libcanberra-pulse}}. See: [https://bbs.archlinux.org/viewtopic.php?pid=1228558 BBS#1228558].
  
=== Default browser ===
+
=== Fonts ===
The simplest way to make Chromium the default browser is to set variable {{Ic|<nowiki>$BROWSER=chromium</nowiki>}} in {{ic|~/.profile}}
+
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:
+
{{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].}}
$ 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:
+
==== Font rendering issues in PDF plugin ====
{{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}}:
+
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.
x-scheme-handler/http=chromium.desktop
+
  
For more info, see [[Xdg-open]].
+
=== Force 3D acceleration ===
  
=== Flash Player ===
+
{{Warning|Disabling the rendering list may cause unstable behaviour, including crashes of the host. See the bug reports in {{ic|chrome://gpu}}.}}
The Adobe Flash plugin can be [[Pacman|installed]] with the package {{Pkg|flashplugin}}, available in the official repositories.  
+
  
While the classic Flash plugin will not be updated for Linux, Chromium can use the Flash plugin from Google Chrome (that uses the new Pepper API). This plugin is available in the [[AUR]] with the {{AUR|chromium-pepper-flash}} or {{AUR|chromium-pepper-flash-stable}} packages.  
+
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.
  
{{Note|Make sure to enable the Flash 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}}.}}
+
=== WebGL ===
  
If Pepper Flash doesn't show up in the plugins list (as is the case for Iron) then disable libflashplayer.so and start with the following command.
+
{{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.}}
iron --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=11.5.31.101
+
 
+
Enable only one flash player at a time by going to {{ic|chrome://plugins}} -> details -> Adobe Flash Player
+
 
+
=== 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 : Chromium-pepper-flash doesn't 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.
+
 
+
{{bc|<nowiki>
+
#!/bin/bash
+
 
+
## written by Mark Lee <bluerider>
+
## 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
+
 
+
function main () {  ## run the main insertion function
+
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
+
cd ~/.adobe/Flash_Player;  ## go to Flash player user directory
+
rm -rf NativeCache AssetCache APSPrivateData2;  ## remove cache
+
}
+
 
+
function start-hal () {  ## start the hal daemon
+
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
+
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
+
</nowiki>}}
+
 
+
=== Open PDF files inside Chromium ===
+
 
+
There are multiple ways of enabling PDF support in Chromium that are detailed below. 
+
 
+
==== Using Google Chrome's libpdf ====
+
 
+
'''libpdf''' is Google's own implementation of a PDF renderer. While compatible, it is currently only part of Chrome releases, not Chromium ones.
+
 
+
The easiest way to add it to the latter is using one of the packages provided in the [[AUR]]:
+
* {{AUR|chromium-stable-libpdf}} for the stable version of the browser.
+
* {{AUR|chromium-libpdf}} for a development version that installs to {{ic|/usr/lib/chromium}} (such as {{AUR|chromium-dev}}).
+
* {{AUR|chromium-browser-libpdf}} for a development version that installs to {{ic|/opt/chromium-browser}} (such as {{AUR|chromium-browser-bin}}).
+
 
+
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
+
$ 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
+
$ ar vx <deb-file>
+
 
+
Extract LZMA 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 ''about: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}}
+
 
+
For information about the installation see [[Browser Plugins#PDF viewer]].
+
 
+
==== Using the KParts plugin ====
+
{{Box||See the main article: [[Browser Plugins#kpartsplugin]]|#E5E5FF|#FCFCFC}}
+
 
+
=== Certificates ===
+
 
+
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 ==
+
{{Box||See the main article: [[Chromium Tips and Tweaks]]|#E5E5FF|#FCFCFC}}
+
 
+
== 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 {{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:
+
{{bc|
+
$ 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:
+
$ sudo chown -R yourusername:yourusergroup /home/yourusername/.config/chromium
+
 
+
=== 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.
+
Chromium will sometimes disable WebGL with certain graphics card configurations. To remedy this, enter {{ic|chrome://flags}} into the URL bar and ''disable'' the ''Disable WebGL'' flag. Alternatively, pass the command-line flag {{ic|--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 {{ic|--ignore-gpu-blacklist}} when starting Chromium, alternatively, go to {{ic|about:flags}} and enable ''Override software rendering list''.
+
There is also the possibility that your graphics card has been blacklisted by Chromium. See [[#Force 3D acceleration]].
  
=== Pulseaudio & PA-Alsa-Bridge & Pepper-Flash ===
+
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}}.
  
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.
+
If none of the above solves your problem, you may be able to visit {{ic|chrome://gpu/}} for additional debugging info.
  
A possible workaround is to use {{ic|pasuspender}} to suspend Pulseaudio and force Chrome to use Alsa directly.
+
=== Distorted GUI ===
  
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}}:
+
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}}.
  
{{hc|~/.asoundrc|
+
=== "Search Google for this image" broken  ===
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.
+
This seems to be a general Chromium for Linux bug, which has been reported upstream: [https://code.google.com/p/chromium/issues/detail?id=473558].
  
{{bc|
+
Version [https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/chromium&id=5c6dde4a40faa3ffcb58a9434c18cc0ac64a75fc 46.0.2490.71-2] fixes this issue.
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].
+
== See also ==
  
== See Also ==
+
* [http://www.chromium.org/Home Chromium homepage]
* [http://www.chromium.org/Home Chromium Homepage]
+
* [http://googlechromereleases.blogspot.com Google Chrome release notes]
* [http://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 14:09, 17 June 2016

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

Installation

The open-source project, Chromium, can be installed with the chromium package. You can also find:

The derived browser, Google Chrome, bundled with Flash Player and Widevine EME (for e.g. Netflix), can be installed with the google-chromeAUR package. You can also find:

Note: Google Chrome revoked 32 bits support, and only supports 64 bits installation
Tip: 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.

Inox

Inox is a privacy-focused patchset which disables Google services, proprietary features, prevents "calling home" and unhides all extensions. Flags are stored in inox-flags.conf. See this GitHub project for details. Otherwise, instructions regarding Chromium apply equally.

  • inox-binAUR - prebuilt binaries.
  • inoxAUR - Allows disabling additional features in PKGBUILD. Takes a long time to build, regardless of your CPU.

Configuration

Set Chromium as default browser

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.

File associations

This behaviour is related to xdg-open: see xdg-open#Configuration. For more information about the topic in general, 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 co-developed by Google and Adobe, and distributed bundled with Google Chrome.

To install Pepper Flash for Chromium, install the chromium-pepper-flashAUR package. If you want the development version, install the chromium-pepper-flash-devAUR package instead.

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.

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. 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.

"Search Google for this image" broken

This seems to be a general Chromium for Linux bug, which has been reported upstream: [1].

Version 46.0.2490.71-2 fixes this issue.

See also