Difference between revisions of "Chromium"
m (→Google Play and Flash: wording) |
m (→Google Play and Flash: rm invalid out-of-date mark) |
||
| Line 177: | Line 177: | ||
=== Google Play and Flash === | === Google Play and 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. See [[Amazon Instant Video]] for information about installing HAL. | 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. See [[Amazon Instant Video]] for information about installing HAL. | ||
Revision as of 17:30, 27 December 2013
Related articles
Chromium is an open source graphical web browser from Google, based on the WebKit rendering engine.
Contents
Installation
The open source project, Chromium, can be installed with the package chromium, available in the official repositories. In the AUR you can also find:
- chromium-devAUR - the development version (beware: compiling Chromium takes at least as long as compiling the Linux kernel!)
- chromium-browser-binAUR - 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 google-chromeAUR, available in the AUR. In the AUR you can also find:
- google-chrome-betaAUR - the beta version
- google-chrome-devAUR - the development version
SRWare Iron, a modified Chromium with altered settings to increase privacy and with built-in ad-blocker, can be installed with the package iron-binAUR, available in the AUR.
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.
Font rendering
Chromium (and Google Chrome) will use the settings in ~/.config/fontconfig/fonts.conf. For possibly better rendering you may try the following. Create the file if it does not already exist.
~/.config/fontconfig/fonts.conf
<match target="font"> <edit mode="assign" name="autohint"><bool>true</bool></edit> <edit mode="assign" name="hinting"><bool>true</bool></edit> <edit mode="assign" name="hintstyle"><const>hintslight</const></edit> </match>
If the fonts are still rendered badly, you can use Xft settings as suggested here:
~/.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:
$ xrdb -merge ~/.Xresources
Non-Latin characters
Install needed fonts to correctly display Chinese, Japanese, Korean characters. For examples of recommended fonts for various languages see Font Packages.
For the Arch Wiki, one only needs the ttf-arphic-uming package.
Flash Player plugin
Adobe (Netscape plugin API)
The Adobe Flash plugin can be installed with the package 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 easiest way to install pepper-flash for Chromium is using one of the packages provided in the AUR:
- chromium-pepper-flash-stableAUR for the stable version.
- chromium-pepper-flashAUR for a development version.
PDF viewer plugin
There are multiple ways of enabling PDF support in Chromium that are detailed below.
libpdf
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:
- chromium-libpdf-stableAUR for the stable version.
- chromium-libpdfAUR for a development version.
Enable the plugin in chrome://plugins.
Manual installation
To do it manually, download a Google Chrome release that corresponds to the version of Chromium you use:
$ 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 libpdf.so from opt/google/chrome/ to the appropriate directory as stated above. A change of its file permissions and ownership may be necessary (the permission of libpdf.so should be 755).
To verify that the installation went correctly: start Chromium, open chrome://plugins/ and check if "Chrome PDF Viewer" is available (it may need to be enabled).
Using mozplugger
Using the KParts plugin
Certificates
Chromium uses NSS for the certificate management. Certificates can be managed in Settings → Show advanced settings... → Manage Certificates....
Tips and tricks
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 --proxy-pac-url and --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:
$ 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 ~/.config/chromium as following:
# chown -R yourusername:yourusergroup ~/.config/chromium
WebGL
Sometimes, Chromium will disable WebGL with certain graphics card configurations. This can generally be remedied by typing about:flags into the URL bar and enabling the WebGL flag. You may also enable WebGL by passing 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. To override this use the --ignore-gpu-blacklist flag or go to about:flags and enable Override software rendering list.
Google Play and 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. See Amazon Instant Video for information about installing HAL.
Force 3D acceleration in Pepper Flash Player and i.g. the browser with radeon driver
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 ATI#Enabling_video_acceleration. You could check if it is working in chrome://gpu.