View source for Chromium (Italiano)

{{i18n|chromium}}
[[Category:Web Browser (Italiano)]]
[[fr:chromium]]
{{translateme}}
{{Nota|Questo articolo è in fase di traduzione. Seguite per ora le istruzioni della versione inglese.}}


Chromium è un browser web grafico di Google, bastato sul motore di rendering [[Wikipedia: WebKit|WebKit]].

== Installazione ==
La versione stabile di Chromium può essere installata dal repository ufficiale con:
 # pacman -S chromium

Esiste anche una versione in via di sviluppo che può essere trovata in [[Arch User Repository]] sotto il nome di {{Package AUR|chromium-dev}}, oltre a {{Package AUR|chromium-update}} che è uno script di aggiornamento che installa o aggiorna alle nightly build di Chromium. Una versione in binario è {{Package AUR|chromium-browser-bin}}.

{{Nota|Compilare chromium-beta o chromium-dev dura all'incirca quanto compilare il kernel Linux.}}
{{Nota|chromium-update installa le nightly build di Chromium che sono pre-compilate dal server Chromium Buildbot}}

Esistono anche alcuni pacchetti in AUR che forniscono la versione in binario di Google Chrome.

Si veda anche [http://news.softpedia.com/news/Google-Chrome-vs-Chromium-Understanding-Stable-Beta-Dev-Releases-and-Version-No-140060.shtml questo articolo] per una spiegazione delle differenze tra i tre flavour, Chromium vs. Chrome, e i numeri di versione.

== Configurazione ==
=== Visualizzare vari caratteri non latini ===
Per visualizzare correttamente caratteri cinesi, giapponesi e coreani, si veda [[Fonts (Italiano)#Pacchetti font|qui]] per istruzioni dettagliate per installare i vari font TrueType.

=== Usare Chromium senza ambiente desktop ===

A differenza di [[Firefox (Italiano)|Firefox]], Chromium non mantiene un proprio database di mimetype-to-application associations. Invece, si affida a {{Filename|xdg-open}} (parte di extra/xdg-utils) per aprire file e, per esempio, [[Wikipedia: Magnet_URI_scheme|magnet link]].

In un [[Desktop Environment|ambiente desktop]] (es. [[GNOME (Italiano)|Gnome]], o [[KDE (Italiano)|Kde]], or [[Xfce (Italiano)|Xfce]]), {{Filename|xdg-open}} passa semplicemente gli argomenti all'applicazione che apre i file di quell'ambiente desktop (rispettivamente {{Filename|gnome-open}}, {{Filename|kde-open}}, o {{Filename|exo-open}}), e ciò significa che le associazioni sono lasciate all'ambiente desktop.

Comunque, quando non vengono rilevati ambienti desktop (per esempio quando viene eseguito un [[Window Manager (Italiano)|window manager]] standalone, come [[Openbox (Italiano)|Openbox]]), il comportamento di{{Filename|xdg-open}} diventa piuttosto strano e irritante: molti tipi di file aperti negli stessi Firefox o Chromium, nessun supporto per magnet link, etc.

Ci sono molte soluzioni a questo problema, delineate qui sotto.

* Improve xdg-open, make it smarter (aka "patches welcome" :P )

* Use part of a desktop environment, specifically, the part which includes the file opener; for gnome, that would be 'libgnome' (and its dependencies), for xfce, 'exo'. The $DE environment variable needs to be exported before starting the window manager. For example:
:{{File|name=~/.xinitrc|content=<nowiki>
export DE=gnome
exec ck-launch-session openbox
</nowiki>}}

* Use {{Package AUR|mimeo}} (written by an arch (trusted) user) and {{Package AUR|xdg-utils-mimeo}}, which replaces extra/xdg-utils and contains a {{Filename|xdg-open}} script patched to make use of {{Filename|mimeo}} the same way {{Filename|gnome-open}} would be used. Mimetype<->application associations can then be customised easily in {{Filename|$XDG_CONFIG_HOME/mimeo.conf}} or {{Filename|~/.config/mimeo.conf}}

* Use pcmanfm file associations (eg. for lxde desktop enviroment users). Change:
:{{File|name=/usr/bin/xdg-open|content=<nowiki>
generic)
pcmanfm "$url"
;;
</nowiki>}}
:or modify your {{Filename|.profile}}
:{{File|name=~/.profile|content=<nowiki>
export DESKTOP_SESSION=LXDE
</nowiki>}}

* When using openbox and no Desktop Environment (=DE) like KDE, GNOME or XFCE do following:
:{{File|name=~/.config/openbox/environment|content=<nowiki>
export BROWSER=chromium
</nowiki>}}

'''Attention: Do not export any DE environment variable!'''

Then, you basically have to fill the {{Filename|~/.local/share/applications/defaults.list}} file with default associations. As this can be painful, some utilities are available:
* xdg-mime: not that intuitive; e.g. to use xpdf as default pdf viewer:
 $ xdg-mime default xpdf.desktop application/pdf
* mimetype ({{Package Official|perl-file-mimeinfo}} package): more intuitive; e.g. to select default application for a given extension (you need a sample file):
 $ mimetype -d file.extension

This should create an entry in your local mime database:
{{File|name=~/.local/share/applications/defaults.list|content=<nowiki>
[Default Applications]
text/html=chromium.desktop
application/pdf=xpdf.desktop
</nowiki>}}
Restart chromium and your pdf files should be opened with xpdf now.

For me it only worked as normal user - as root I had problems cause no directories for the local mime times were created. See also [https://bbs.archlinux.org/viewtopic.php?id=93956 this thread].

You could also try installing {{Package Official|perl-file-mimeinfo}}

=== Font Rendering ===
Chromium is now supposed to use the settings in {{Filename|~/.fonts.conf}}, though you may have to edit it manually (see [[Font_Configuration#Basic_settings|Font Configuration]]). If the fonts are still rendered badly you can use xft settings [[Xdefaults|as suggested here]]. Just create {{Filename|~/.Xdefaults}} if it does not exist and add in:
<pre>
! Xft settings ---------------------------------------------------------------

Xft.dpi:        96
Xft.antialias:  true
Xft.rgba:       rgb
Xft.hinting:    true
Xft.hintstyle:  hintslight
</pre>

{{Note|these settings will affect any application that reads {{Filename|~/.Xdefaults}}, not just Cromium; one example is [[Rxvt-unicode|rxvt-unicode]].}}

=== Default browser ===
The simplest way to make Chromium the default browser is to set variable {{Codeline|<nowiki>$BROWSER=chromium</nowiki>}} in {{Filename|~/.profile}}
 if [ -n "$DISPLAY" ]; then
      BROWSER=chromium
 fi

The other way is to edit the ''xdg-open'' script.
 $ sudo $YOUR_EDITOR /usr/bin/xdg-open
At almost the bottom on the file, is a long horizontal list of browsers:
 if [ x"$DE" = x"" ]; then
    # if BROWSER variable is not set, check some well known browsers instead
    if [ x"$BROWSER" = x"" ]; then
        BROWSER=links2:links:lynx:w3m
        if [ -n "$DISPLAY" ]; then
            BROWSER=firefox:mozilla:epiphany:konqueror:chromium-browser:google-chrome:$BROWSER
        fi
    fi
    DE=generic
 fi
Add '''chromium:''' ''(mind the colon which separates the entries)'' before '''firefox:mozilla:''' ... and save. 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 '''mimeo''', is to associate "http://" links with chromium:
{{File|name=~/.config/mimeo.conf|content=<nowiki>
/usr/bin/chromium
  ^http://
</nowiki>}}

If all of that still does not get it working, you can try adding the following to the {{Codeline|[Added Associations]}} list in  {{Filename|~/.local/share/applications/mimeapps.list}}
 x-scheme-handler/http=chromium.desktop

=== Flash Player ===

If running i686 Arch Linux, all one needs to do is to install the flash plugin and restart chromium:
 # pacman -S flashplugin

For x86_64, one [http://www.archlinux.org/news/508/ needs to enable] the new [multilib] repository.
 # pacman -S flashplugin

=== 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. Adobe Reader via the mozplugger plugin.
KDE users can also choose KParts Plugin and use any installed KDE application as an embedded viewer.   

==== libpdf.so ====

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 — {{Package AUR|chromium-stable-libpdf}} for the stable version of the browser, or for the dev version either {{Package AUR|chromium-libpdf}} if your Chromium package installed to {{Filename|/usr/lib/chromium}} or {{Package AUR|chromium-browser-libpdf}} if it installed to {{Filename|/opt/chromium-browser}}.

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 {{Filename|libpdf.so}} from {{Filename|opt/google/chrome/}} to the appropriate directory as stated above. A change of its file permissions and ownership may be necessary (the permission of {{Filename|libpdf.so}} should be 755).

Start Chromium and open ''about:plugins''. "Chrome PDF Viewer" should now view; it may need to be enabled.

{{Note|As a new version of Chromium will not update {{Filename|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 ====

To use mozplugger, install {{Package AUR|mozplugger-chromium}} from AUR.
Follow similar instructions as described in [[Firefox Tweaks]] to set up the PDF app you wish to use with mozplugger-chromium.

==== kpartsplugin ====

To use KParts Plugin, install {{Package AUR|kpartsplugin}} from AUR.
The plugin should be able, among other things, to open PDF files inside Chromium using an embedded Okular instance.

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

== Tips and tricks ==

=== Controlling Memory Usage ===

* Chromium offers some command-line options to help control how efficient it is with system memory, by determining how often it should release memory back to the operating system.  It is done with the flag ''--memory-model=X'', where X is either ''high'', ''medium'', or ''low''.  Setting it to high makes chromium never release memory.  Medium makes it reduce its working set of the memory when switching tabs, and low makes it reduce its working set when switching tabs and when the browser is not actively being used.  In my experience, running chromium with ''--memory-model=low'' can actually improve performance as well, though your mileage may vary.  --[[User:Falcata|Falcata]] 06:07, 26 November 2010 (EST)

===Link file manager to "Show in folder" function===
When you are using a window manager such as Openbox in combination with a file manager like Thunar instead of a DE, this function of Chromium may only show the directory tree inside Chromium. However to show the file in the folder using your file manager instead, install {{Filename|perl-file-mimeinfo}}.

=== Icons not shown in download tab ===

You may find that Chromium shows icon placeholders (icons representing broken documents) instead of appropriate icons in its download tab. The likely cause is that you have not installed a desktop environment.

Remedy this by installing GNOME icons:

 # pacman -S gnome-icon-theme

=== Cache in tmpfs ===
For SSD users, it is nice to have the cache of Chromium in a tmpfs, but there is no need to have the whole profile in a tmpfs (see below). Someone posted [https://bbs.archlinux.org/viewtopic.php?pid=967385#p967385 here] a solution for this.

Close Chromium before starting! Replace ''your_user'' with your username.

Add the following to {{Filename|/etc/fstab}}:
 cache-chromium /home/your_user/.cache/chromium tmpfs defaults,noatime,mode=1777 0 0

Then delete & recreate the cache folder of Chromium:
 rm -r /home/your_user/.cache/chromium
 mkdir /home/your_user/.cache/chromium

Restart your machine or do '''sudo mount -a'''

Afterwards, Chromium's cache should be in RAM. You can check that with '''df -h'''. 

There is also a command line parameter for placing the cache somewhere else:
 --disk-cache-dir=/tmp
This could be another solution, if {{Filename|/tmp}} is in RAM for example.

=== Profile in tmpfs ===
The default Chromium profile is located in {{Filename|~/.config/chromium}}. This profile can be relocated to an available [http://en.wikipedia.org/wiki/Tmpfs tmpfs] filesystem, including {{Filename|/tmp}}, or {{Filename|/dev/shm}} for improvements in application response as the the entire profile is now stored in RAM. Another benefit is a reduction in disk read and write operations, of which SSDs benefit the most.

==== Simple bash script to automate the process ====
Use the following Bash script to automatically move your Chromium profile to {{Filename|/dev/shm}} and keep it synchronized.

{{Filename|$HOME/bin/sync-chromium}}:
<pre>#!/bin/bash

STATIC=$HOME/.config/chromium-backup
LINK=$HOME/.config/chromium
VOLATILE=/dev/shm/.chromium

[[ ! -d $VOLATILE/cache ]] && mkdir -p $VOLATILE/cache
[[ ! -h $HOME/.cache/chromium ]] && ln -s $VOLATILE/cache $HOME/.cache/chromium
[[ -r $VOLATILE ]] || install -dm755 $VOLATILE

if [[ `readlink $LINK` != $VOLATILE ]]; then
  mv $LINK $STATIC
  ln -s $VOLATILE $LINK
fi

if [[ -e $LINK/.flagged ]]; then
  rsync -a --delete --exclude .flagged $LINK/ $STATIC/
else
  rsync -a $STATIC/ $LINK/
  touch $LINK/.flagged
fi</pre>

Do not forget to make it executable:

 $ chmod +x $HOME/bin/sync-chromium

Call the script at login by copying the following to your {{Filename|~/.config/autostart}}

{{Filename|~/.config/autostart/sync-chromium.desktop}}:
<pre>
[Desktop Entry]
Type=Application
Exec=$HOME/bin/sync-chromium
Hidden=false
Name=ff-sync
</pre>

====Add a cron job to keep it updated====
Manipulate the user's [[cron]] table using {{codeline|crontab}}:
 $ crontab -e

Add a line to start the script every 30 minutes,
 */30 * * * * ''~/bin/sync-chromium''
or add the following to do so every 2 hours:
 0 */2 * * * ''~/bin/sync-chromium''

====Add an entry to {{Filename|/etc/rc.local.shutdown}}====
Finally, a line to {{Filename|/etc/rc.local.shutdown}} will keep your profile synchronized when the machine is shutdown.

{{Note|Replace the word "user" with the user name of interest in the following line.}}
 # echo "su user -c /home/user/bin/sync-chromium" >> /etc/rc.local.shutdown

=== Enabling experimental features ===
To enable experimental features of Chromium like WebGL and rendering webpages with the GPU, type "about:flags" in the Chromium address bar and enable features you want.
=== Search Engines ===
You can make sites like wiki.archlinux.org and wikipedia.org easily searchable by first executing a search on those pages, then going to Options>Preferences>Basics and clicking "Manage" in the "Default Search" section. You can then, for example, "Edit" the Wikipedia entry and change its keyword to "w". Then, you can search Wikipedia for "Arch Linux" from the address bar by simply entering "w arch linux". "?" is a hard-coded keyword for Google search (it will behave differently from the other keywords). It allows you to easily search for things like "/bin/bash".

== Troubleshooting ==
=== Default profile ===
If you cannot get your default profile when you try to run chromium:
<pre>
$ chromium
[2630:2630:485325611:FATAL:chrome/browser/browser_main.cc(755)] Check failed: profile. 
Cannot get default profile. Trace/breakpoint trap
</pre>

Just correct the owner of the directory {{Filename|~/.config/chromium}}, and it will work.
<pre>
$sudo chown -R yourusername:yourusergroup /home/yourusername/.config/chromium
</pre>

== Resources ==
* [http://www.chromium.org/Home Chromium homepage]
* [[Wikipedia: Chromium_(web_browser)#Differences_from_Google_Chrome|Differences from Google Chrome]]
* [http://googlechromereleases.blogspot.com/ Announcements and release notes for the Google Chrome browser]