Difference between revisions of "Chromium"

From ArchWiki
Jump to: navigation, search
(Non-Latin characters: added bit for arch wiki niceness)
m (Losing cookies when switching between desktop environments: clean up link)
 
(276 intermediate revisions by 66 users not shown)
Line 1: Line 1:
 +
[[Category:Web browser]]
 +
[[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 ==
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}} - a development version of the Chromium browser.
 
* {{AUR|chromium-update}} - an update. script for Chromium nighly builds, pre-compiled on the Chromium buildbot server.
 
* {{AUR|chromium-browser-bin}} - a binary version of the latest Chromium build.
 
* {{AUR|iron-bin}} - a binary version of Chromium without Google's 'tracking features'
 
 
{{Note|Compiling {{AUR|chromium-dev}} takes at least as long as compiling the Linux kernel.}}
 
 
Various versions of the modified Google Chrome browser can be found in the [[AUR]]:
 
* {{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.
 
 
== Configuration ==
 
 
=== File associations ===
 
 
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]].
 
 
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*}}.
 
 
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:
 
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}}.
 
 
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:
 
{{hc|/usr/bin/xdg-open|<nowiki>
 
detectDE
 
 
if [ x"$DE" = x"" ]; then
 
    DE=generic
 
fi
 
 
DEBUG 2 "Selected DE $DE"
 
 
# if BROWSER variable is not set, check some well known browsers instead
 
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
+
The open-source project, '''Chromium''', can be [[install]]ed with the {{Pkg|chromium}} package.
    kde)
 
    open_kde "$url"
 
    ;;
 
  
    gnome*)
+
Other alternatives include:
    open_gnome "$url"
 
    ;;
 
  
    mate)
+
* {{App|Chromium Beta Channel|the beta version|https://googlechromereleases.blogspot.com/|{{AUR?|chromium-beta}}}}
    open_mate "$url"
+
* {{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}}}}
  
    xfce)
+
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.
    open_xfce "$url"
 
    ;;
 
  
    lxde)
+
Other alternatives include:
    open_lxde "$url"
 
    ;;
 
  
    generic)
+
* {{App|Google Chrome Beta Channel|the beta version|https://www.google.com/chrome/browser/beta.html|{{AUR|google-chrome-beta}}}}
    open_generic "$url"
+
* {{App|Google Chrome Dev Channel|the development version|https://www.google.com/chrome/browser/|{{AUR|google-chrome-dev}}}}
    ;;
 
  
    *)
+
{{Note|
    exit_failure_operation_impossible "no method available for opening '$url'"
+
* Google Chrome dropped 32 bits support, and only supports 64 bits installation.
    ;;
+
* 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.
esac</nowiki>
 
 
}}
 
}}
  
change the third line: {{ic|DE&#61;generic}} to one of the supported desktop environments (e.g. {{ic|DE&#61;gnome}}).  
+
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.
  
{{Note|These changes are lost when any of the utilities are upgraded.}}
+
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]].
  
An approach which is less useful is to place the required application in the default browser list:
+
== Configuration ==
  
    BROWSER=links2:links:lynx:w3m
+
=== Default applications ===
    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.
+
To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see [[default applications]].
  
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].
+
=== Flash Player plugin ===
  
=== Font Rendering ===
+
Flash Player is automatically installed when using Google Chrome.
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:
+
To install it for Chromium, [[install]] the {{Pkg|pepper-flash}} package.
  
{{bc|xrdb -merge ~/.Xresources}}
+
Make sure Flash is allowed to run in {{ic|chrome://settings/content/flash}}.
  
{{Note|These settings will affect any application that uses X Resources for font settings; one example is [[Rxvt-unicode|rxvt-unicode]].}}
+
=== Widevine Content Decryption Module plugin ===
  
==== Non-Latin characters ====
+
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.
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 install it for Chromium, [[install]] the {{AUR|chromium-widevine}} package. Make sure ''Allow sites to play protected content'' is checked in {{ic|chrome://settings/content/protectedContent}}.
  
=== Default browser ===
+
=== PDF viewer plugin ===
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:
+
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 {{ic|chrome://settings/content/pdfDocuments}}.
$ 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:
+
=== Certificates ===
{{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}}:
+
Chromium uses [[Network Security Services|NSS]] for certificate management. Certificates can be managed in {{ic|chrome://settings/certificates}}.
x-scheme-handler/http=chromium.desktop
 
  
For more info, see [[Xdg-open]].
+
== Tips and tricks ==
  
=== Flash Player ===
+
See the main article: [[Chromium/Tips and tricks]].
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.
+
== Troubleshooting ==
  
{{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}}.}}
+
=== Fonts ===
  
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.
+
{{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].}}
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
+
==== Font rendering issues in PDF plugin ====
  
=== Google Play & Flash ===
+
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.
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}}.
+
=== Force 3D acceleration ===
  
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 :
+
{{Warning|Disabling the rendering blacklist may cause unstable behaviour, including crashes of the host. See the bug reports in {{ic|chrome://gpu}}.}}
{{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.
+
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.
{{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.
+
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.
  
{{bc|<nowiki>
+
=== WebGL ===
#!/bin/bash
+
{{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.}}
 
 
## 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
+
There is the possibility that your graphics card has been blacklisted by Chromium. See [[#Force 3D acceleration]].
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
+
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}}.
cd ~/.adobe/Flash_Player;  ## go to Flash player user directory
 
rm -rf NativeCache AssetCache APSPrivateData2;  ## remove cache
 
}
 
  
function start-hal () { ## start the hal daemon
+
Visit {{ic|chrome://gpu/}} for debugging information about WebGL support.
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
+
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}}.
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
+
=== Distorted GUI ===
</nowiki>}}
 
  
=== Open PDF files inside Chromium ===
+
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}}.
  
There are multiple ways of enabling PDF support in Chromium that are detailed below. 
+
=== Disable keyring password prompt ===
  
==== Using Google Chrome's libpdf ====
+
{{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}}
  
'''libpdf''' is Google's own implementation of a PDF renderer. While compatible, it is currently only part of Chrome releases, not Chromium ones.
+
See [[GNOME/Keyring#Passwords are not remembered]]. You may also need to edit the Chromium command line to append {{ic|1=--password-store=gnome}}.
  
The easiest way to add it to the latter is using one of the packages provided in the [[AUR]]:
+
=== Chromecasts in the network are not discovered ===
* {{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:
+
You will need to enable the Media Router Component Extension in {{ic|chrome://flags/#load-media-router-component-extension}}.
  
$ wget https://dl-ssl.google.com/linux/direct/google-chrome-stable_current_i386.deb
+
=== Losing cookies when switching between desktop environments ===
$ 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
+
See [[Chromium/Tips and tricks#Force a password store]].
$ 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.
 
 
 
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].
+
== See also ==
  
== See Also ==
+
* [https://www.chromium.org/ Chromium homepage]
* [http://www.chromium.org/Home Chromium Homepage]
+
* [https://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:07, 24 July 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

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

Flash Player is automatically installed when using Google Chrome.

To install it for Chromium, install the pepper-flash package.

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

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

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 chrome://settings/content/pdfDocuments.

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

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.

Losing cookies when switching between desktop environments

See Chromium/Tips and tricks#Force a password store.

See also