Difference between revisions of "Chromium"

From ArchWiki
Jump to: navigation, search
(Installation: style)
(cleaned up a bit: phrasing, style, links and whatnot)
Line 4: Line 4:
 
[[zh-CN:Chromium]]
 
[[zh-CN:Chromium]]
 
[[Category:Web Browser]]
 
[[Category:Web Browser]]
 
  
 
{{Article summary start}}
 
{{Article summary start}}
{{Article summary text|General info and installation as well as troubleshooting for Chromium.}}
+
{{Article summary text|General information, installation and troubleshooting for Chromium.}}
{{Article summary heading|External Resources}}
+
{{Article summary link|Announcements and release notes for the Google Chrome browser|http://googlechromereleases.blogspot.com}}
+
{{Article summary link|Chromium homepage|http://www.chromium.org/Home}}
+
[[Wikipedia: Chromium_(web_browser)#Differences_from_Google_Chrome|Differences from Google Chrome]]
+
 
{{Article summary heading|Related}}
 
{{Article summary heading|Related}}
{{Article summary wiki|Chromium_Tips_and_Tweaks}}
+
{{Article summary wiki|Chromium Tips and Tweaks}}
 +
{{Article summary wiki|Browser Plugins}}
 +
{{Article summary wiki|Firefox}}
 +
{{Article summary wiki|Opera}}
 
{{Article summary end}}
 
{{Article summary end}}
  
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 Google, based on the [[Wikipedia:WebKit|WebKit]] rendering engine.
  
 
== Installation ==
 
== Installation ==
Line 39: Line 37:
 
=== File associations ===
 
=== File associations ===
  
Unlike [[Firefox]], Chromium does not maintain its own database of mimetype-to-application associations. Instead, it relies on [[Xdg-open]] to open files and other mime types, for example, [[Wikipedia: Magnet_URI_scheme|magnet links]]. See [[Xdg-open]] for more information.
+
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 xdg-email which is similar to xdg-open. Other protocol handlers may have equivalent scripts so check /usr/bin/xdg*.  
+
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 both is broken in places when used in an environment that is not one of the major four or five: gnome, kde, xfce and lxde. 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 won't so trying each is recommended. It has been reported that desktop environment can be set as an environment variable:
+
  
 +
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
 
  export DE=INSERT_DE_HERE
  
where the recognised DEs are: gnome, kde, xfce and lxde. Put it somewhere like ~/.xinitrc. This might impact on other things though.
+
where the recognised DEs 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 script: xdg-open or xdg-email to hardcode a useful DE. At the bottom of the file you will see something like this:
+
An alternative is to edit the {{ic|xdg-open}} or {{ic|xdg-email}} scripts and '''hardcode''' a useful DE. At the bottom of the file you will see something like this:
 +
{{hc|/usr/bin/xdg-open|<nowiki>
 +
detectDE
  
detectDE
+
if [ x"$DE" = x"" ]; then
if [ x"$DE" = x"" ]; then
+
 
     DE=generic
 
     DE=generic
fi
+
fi
# if BROWSER variable is not set, check some well known browsers instead
+
 
if [ x"$BROWSER" = x"" ]; then
+
DEBUG 2 "Selected DE $DE"
     BROWSER=links2:links:lynx:w3m
+
 
 +
# 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
 
     if [ -n "$DISPLAY" ]; then
         BROWSER=firefox:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER
+
         BROWSER=x-www-browser:firefox:seamonkey:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER
 
     fi
 
     fi
fi
+
fi
case "$DE" in
+
 
 +
case "$DE" in
 
     kde)
 
     kde)
 
     open_kde "$url"
 
     open_kde "$url"
 
     ;;
 
     ;;
 +
 
     gnome*)
 
     gnome*)
 
     open_gnome "$url"
 
     open_gnome "$url"
 
     ;;
 
     ;;
 +
 +
    mate)
 +
    open_mate "$url"
 +
    ;;
 +
 
     xfce)
 
     xfce)
 
     open_xfce "$url"
 
     open_xfce "$url"
 
     ;;
 
     ;;
 +
 
     lxde)
 
     lxde)
 
     open_lxde "$url"
 
     open_lxde "$url"
 
     ;;
 
     ;;
 +
 
     generic)
 
     generic)
 
     open_generic "$url"
 
     open_generic "$url"
 
     ;;
 
     ;;
 +
 
     *)
 
     *)
 
     exit_failure_operation_impossible "no method available for opening '$url'"
 
     exit_failure_operation_impossible "no method available for opening '$url'"
 
     ;;
 
     ;;
esac
+
esac</nowiki>
 +
}}
  
change the 3rd line: {{ic|<nowiki>DE=generic</nowiki>}} to one of the DEs eg {{ic|<nowiki>DE=gnome</nowiki>}}.  
+
change the third line: {{ic|DE&#61;generic}} to one of the supported desktop environments (e.g. {{ic|DE&#61;gnome}}).  
 +
 
 +
{{Note|These changes are lost when any of the utilities are upgraded.}}
  
 
An approach which is less useful is to place the required application in the default browser list:
 
An approach which is less useful is to place the required application in the default browser list:
Line 92: Line 106:
 
     fi
 
     fi
  
Xdg-open and 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 eg your mail client will open but no compose window with the mailto address. Also it will only work for one application.
+
{{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.
  
The problem with these approaches is that the changes are lost when these utilities are upgraded.
+
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].
 
+
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. These ideas came from a [[https://bbs.archlinux.org/viewtopic.php?id=81282&p=1 bbs discussion]]
+
  
 
=== Font Rendering ===
 
=== Font Rendering ===
Line 102: Line 114:
 
{{hc|~/.Xresources|
 
{{hc|~/.Xresources|
 
...
 
...
 
 
! Xft settings ---------------------------------------------------------------
 
! Xft settings ---------------------------------------------------------------
 
 
Xft.dpi:        96
 
Xft.dpi:        96
 
Xft.antialias:  true
 
Xft.antialias:  true
Line 110: Line 120:
 
Xft.hinting:    true
 
Xft.hinting:    true
 
Xft.hintstyle:  hintslight
 
Xft.hintstyle:  hintslight
 
 
...
 
...
 
}}
 
}}
Line 121: Line 130:
  
 
==== Non-Latin characters ====
 
==== Non-Latin characters ====
Install needed fonts to correctly display Chinese, Japanese, Korean characters. For example, [[pacman|Install]] {{Pkg|ttf-arphic-uming}}, available in the [[Official Repositories]].
+
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 more, see the  [[Fonts#Font_packages|Font Packages]] for detailed instructions.
+
  
 
=== Default browser ===
 
=== Default browser ===
Line 132: Line 139:
  
 
To test if this were conducted successfully, type this into your terminal:
 
To test if this were conducted successfully, type this into your terminal:
  $ xdg-open http://google.com
+
  $ xdg-open http://google.com/
 
If everything went perfect, either a new tab inside Chromium, or a new window would open and display the Google homepage, depending on your settings.
 
If everything went perfect, 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 '''mimeo''', is to associate "http://" links with chromium:
+
Another option, when using {{AUR|mimeo}}, is to associate "http://" links with Chromium:
 
{{hc|~/.config/mimeo.conf|<nowiki>
 
{{hc|~/.config/mimeo.conf|<nowiki>
 
/usr/bin/chromium
 
/usr/bin/chromium
Line 141: Line 148:
 
</nowiki>}}
 
</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}}
+
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
 
  x-scheme-handler/http=chromium.desktop
  
Line 147: Line 154:
  
 
=== Flash Player ===
 
=== Flash Player ===
 +
The Adobe Flash plugin can be [[Pacman|installed]] with the package {{Pkg|flashplugin}}, available in the official repositories.
  
All one needs to do is to [[pacman|install]] the {{Pkg|flashplugin}} package and restart Chromium.
+
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}}, {{AUR|chromium-pepper-flash-stable}} or {{AUR|chrome-pepper-flashplugin}} packages.  
  
If you wish to use Flash Player using Pepper API, you can install {{AUR|chromium-pepper-flash}}, {{AUR|chromium-pepper-flash-stable}} or {{AUR|chrome-pepper-flashplugin}} from [[AUR]] and enable only the flash plugin with location {{ic|/usr/lib/PepperFlash/libpepflashplayer.so}} in {{ic|chrome://plugins}}.
+
{{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}}.}}
  
 
=== Open PDF files inside Chromium ===
 
=== Open PDF files inside Chromium ===
  
There are two ways to do this: The first one by using Google Chrome's own PDF rendering plugin, the second by allowing Chromium access to e.g. Evince via the mozplugger plugin.
+
There are multiple ways of enabling PDF support in Chromium that are detailed below.
KDE users can also choose KParts Plugin and use any installed KDE application as an embedded viewer. 
+
  
==== libpdf.so ====
+
==== 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.
+
'''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, or for the dev version either {{AUR|chromium-libpdf}} if your Chromium package installed to {{ic|/usr/lib/chromium}} or {{AUR|chromium-browser-libpdf}} if it installed to {{ic|/opt/chromium-browser}}.
+
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:
 
To do it manually, download a Google Chrome release that corresponds to the version of Chromium you use:
Line 172: Line 182:
  
 
Extract the deb file with
 
Extract the deb file with
 
 
  $ ar vx <deb-file>
 
  $ ar vx <deb-file>
  
 
Extract LZMA archive with
 
Extract LZMA archive with
 
 
  $ tar -xJf <lzma-file>
 
  $ 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).
 
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).
  
Start Chromium and open ''about:plugins''. "Chrome PDF Viewer" should now view; it may need to be enabled.
+
To verify 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.}}
 
{{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.}}
  
==== mozplugger ====
+
==== Using mozplugger ====
 +
[http://mozplugger.mozdev.org/ mozplugger] is a general purpose Firefox plugin that allows the user to embed and launch their favourite application to handle the various different types of media. It can also be used in Chromium to handle PDF files using Evince or Okular, for example.
 +
 
 +
mozplugger plugin can be [[Pacman|installed]] with the package {{AUR|mozplugger-chromium}}, available in the AUR.
  
To use mozplugger, install {{AUR|mozplugger-chromium}} from AUR.
+
To set the application you wish to use to view PDF files, follow the instructions on the [[Firefox_Tweaks#Viewing_PDF.2FPS_inside_Firefox|Firefox Tweaks]] page.
Follow similar instructions as described in [[Firefox Tweaks]] to set up the PDF app you wish to use with mozplugger-chromium.
+
  
==== kpartsplugin ====
+
==== Using the KParts plugin ====
 +
[http://www.unix-ag.uni-kl.de/~fischer/kpartsplugin/ The KParts plugin] is a plugin that uses KDE's KPart technology to embed different file viewers in the browser, such as PDFs (using Okular), archives (using Ark), ODF (using Calligra Words), etc.
  
To use KParts Plugin, install {{Pkg|kpartsplugin}}.
+
The KParts plugin can be installed with the package {{Pkg|kpartsplugin}}, available in the official repositories.
The plugin should be able, among other things, to open PDF files inside Chromium using an embedded Okular instance.
+
  
 
=== Certificates ===
 
=== Certificates ===
  
Chromium uses [[Nss | NSS]] for the certificate management. Certificates can be managed (including added) by going to Wrench -> Preferences -> Under the Hood -> Manage 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 ==
 
== Tips and Tricks ==
This section has been distilled out into a discrete [[Chromium_Tips_and_Tweaks]] article.
+
{{Box||See the main article: [[Chromium Tips and Tweaks]]|#E5E5FF|#FCFCFC}}
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
 
=== Proxy Settings ===
 
=== Proxy Settings ===
Proxy settings do not work properly. Especially when used through the KDE interface. A good method as of now is to use the command line options like {{ic|--proxy-pac-url}} and {{ic|--proxy-server}}
+
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 ===
 
=== Default profile ===
If you cannot get your default profile when you try to run chromium:
+
If you cannot get your default profile when you try to run Chromium and get a similar error instead:
 
{{bc|
 
{{bc|
 
$ chromium
 
$ chromium
Line 215: Line 225:
 
}}
 
}}
  
Just correct the owner of the directory {{ic|~/.config/chromium}}, and it will work.
+
you have to set the correct owner of the directory {{ic|~/.config/chromium}} as following:
{{bc|
+
$ sudo chown -R yourusername:yourusergroup /home/yourusername/.config/chromium
$sudo chown -R yourusername:yourusergroup /home/yourusername/.config/chromium
+
}}
+
  
 
=== WebGL ===
 
=== WebGL ===
Line 224: Line 232:
 
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 the WebGL flag. You may also enable WebGL by passing the command line flag {{ic|--enable-webgl}} to Chromium in the terminal.
 
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 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}} to the chromium command.
+
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''.
 +
 
 +
== See Also ==
 +
* [http://www.chromium.org/Home Chromium Homepage]
 +
* [http://googlechromereleases.blogspot.com Google Chrome Release Notes]
 +
* [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]

Revision as of 12:08, 29 September 2012


Summary help replacing me
General information, installation and troubleshooting for Chromium.
Related
Chromium Tips and Tweaks
Browser Plugins
Firefox
Opera

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

Installation

Chromium can be installed with the package chromium, available in the official repositories.

In the AUR you can also find:

  • chromium-devAUR - a development version of the Chromium browser.
  • chromium-updateAUR - an update. script for Chromium nighly builds, pre-compiled on the Chromium buildbot server.
  • chromium-browser-binAUR - a binary version of the latest Chromium build.
Note: Compiling chromium-devAUR takes at least as long as compiling the Linux kernel.

Various versions of the modified Google Chrome browser can be found in the AUR:

See these two 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 to open files and other mime types, for example, magnet links.

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 /usr/bin/xdg*.

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:

export DE=INSERT_DE_HERE

where the recognised DEs are: gnome, kde, xfce and lxde. For the variable to be always set, put it somewhere like ~/.xinitrc or ~/.bashrc.

An alternative is to edit the xdg-open or xdg-email scripts and hardcode a useful DE. At the bottom of the file you will see something like this:

/usr/bin/xdg-open
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. DE=gnome).

Note: These changes are lost when any of the utilities are upgraded.

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

Font Rendering

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:

~/.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
Note: These settings will affect any application that uses X Resources for font settings; one example is rxvt-unicode.

Non-Latin characters

Install needed fonts to correctly display Chinese, Japanese, Korean characters. For examples of recommended fonts for various languages see Font Packages.

Default browser

The simplest way to make Chromium the default browser is to set variable $BROWSER=chromium in ~/.profile

if [ -n "$DISPLAY" ]; then
     BROWSER=chromium
fi

To test if this were conducted successfully, type this into your terminal:

$ xdg-open http://google.com/

If everything went perfect, 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 mimeoAUR, is to associate "http://" links with Chromium:

~/.config/mimeo.conf
/usr/bin/chromium
  ^http://

If all of that still does not get it working, you can try adding the following to the [Added Associations] list in ~/.local/share/applications/mimeapps.list:

x-scheme-handler/http=chromium.desktop

For more info, see Xdg-open.

Flash Player

The Adobe Flash plugin can be installed with the package 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 chromium-pepper-flashAUR, chromium-pepper-flash-stableAUR or chrome-pepper-flashpluginAUR packages.

Note: Make sure to enable the Flash plugin with location /usr/lib/PepperFlash/libpepflashplayer.so in chrome://plugins and disable the plugin with location /usr/lib/mozilla/plugins/libflashplayer.so.

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:

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

mozplugger is a general purpose Firefox plugin that allows the user to embed and launch their favourite application to handle the various different types of media. It can also be used in Chromium to handle PDF files using Evince or Okular, for example.

mozplugger plugin can be installed with the package mozplugger-chromiumAUR, available in the AUR.

To set the application you wish to use to view PDF files, follow the instructions on the Firefox Tweaks page.

Using the KParts plugin

The KParts plugin is a plugin that uses KDE's KPart technology to embed different file viewers in the browser, such as PDFs (using Okular), archives (using Ark), ODF (using Calligra Words), etc.

The KParts plugin can be installed with the package kpartsplugin, available in the official repositories.

Certificates

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

Template:Box

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:

$ 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 about:flags into the URL bar and enabling the 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.

See Also