Difference between revisions of "Chromium"
|Line 192:||Line 192:|
==== Using mozplugger ====
==== Using mozplugger ====
the [[PDF ]].
==== Using the KParts plugin ====
==== Using the KParts plugin ====
=== Certificates ===
=== Certificates ===
Revision as of 10:11, 21 October 2012
zh-CN:ChromiumTemplate:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end Chromium is an open source graphical web browser from Google, based on the WebKit rendering engine.
- 1 Installation
- 2 Configuration
- 3 Tips and Tricks
- 4 Troubleshooting
- 5 See Also
In the AUR you can also find:
- AUR - a development version of the Chromium browser.
- AUR - an update. script for Chromium nighly builds, pre-compiled on the Chromium buildbot server.
- AUR - a binary version of the latest Chromium build.
Various versions of the modified Google Chrome browser can be found in the AUR:
There are exceptions to this rule though. In the case of mailto URIs, Chromium calls out to
xdg-email which is similar to
xdg-open. Other protocol handlers may have equivalent scripts so check
The behaviour of
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:
where the recognised desktop environments are: gnome, kde, xfce and lxde. For the variable to be always set, put it somewhere like
An alternative is to edit the
xdg-email scripts and hard-code a useful DE. At the bottom of the file you will see something like this:
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 kde) open_kde "$url" ;; gnome*) open_gnome "$url" ;; mate) open_mate "$url" ;; xfce) open_xfce "$url" ;; lxde) open_lxde "$url" ;; generic) open_generic "$url" ;; *) exit_failure_operation_impossible "no method available for opening '$url'" ;; esac
change the third line:
DE=generic to one of the supported desktop environments (e.g.
An approach which is less useful is to place the required application in the default browser list:
BROWSER=links2:links:lynx:w3m if [ -n "$DISPLAY" ]; then BROWSER=firefox:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER fi
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.
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 this forum thread.
Chromium is now supposed to use the settings in
~/.fonts.conf, though you may have to edit it manually (see Font Configuration). If the fonts are still rendered badly, you can use Xft settings as suggested here. Create
~/.Xresources if it does not exist and add in:
... ! 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
Install needed fonts to correctly display Chinese, Japanese, Korean characters. For examples of recommended fonts for various languages see Font Packages.
The simplest way to make Chromium the default browser is to set variable
if [ -n "$DISPLAY" ]; then BROWSER=chromium fi
To test if this was applied successfully, try to open an URL with
xdg-open as follows:
$ 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 usingAUR, is to associate "http://" links with Chromium:
If all of that still does not get it working, you can try adding the following to the
[Added Associations] list in
For more info, see Xdg-open.
The Adobe Flash plugin can be installed with the package , 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 or AUR packages.
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 for the stable version of the browser.
/usr/lib/chromium(such as AUR).
AUR for a development version that installs to
/opt/chromium-browser(such as AUR). AUR for a development version that installs to
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>
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 about:plugins and check if "Chrome PDF Viewer" is available (it may need to be enabled).
For information about the installation see Browser Plugins#PDF viewer.
Using the KParts plugin
Chromium uses 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
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-server, to set your proxy.
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:
$ sudo chown -R yourusername:yourusergroup /home/yourusername/.config/chromium
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, pass the flag
--ignore-gpu-blacklist when starting Chromium, alternatively, go to
about:flags and enable Override software rendering list.