Define google-chrome as default Web browser in Thunderbird

To define google-chrome as default Web browser in Thunderbird, there is two steps to follow.
Step 1 (may be enough):
 - open advanced configuration editor (Edit->Preferences->Advanced->Configuration  Editor)
 - define following properties with /usr/bin/google-chrome
network.protocol-handler.app.http
network.protocol-handler.app.https

Step 2:
Usually there is embedded configuration in mimeTypes.rdf file of your Thunderbird profile. In this case, step 1 is not enough.

To define default Web browser:

 - open advanced configuration editor (Edit->Preferences->Advanced->Configuration  Editor)

 - define following properties with true

network.protocol-handler.warn-external.http

network.protocol-handler.warn-external.https

 - open a http link -> the first time there will be a popup, define /usr/bin/google-chrome as your default Web browser, and activate the check box for memorizing this configuration

 - open a https link -> and do the same

You will see that mimeTypes.rdf file will have been edited.

This time, google-chrome will really be the default Web browser in Thunderbird.

Fix google-chrome "error while loading shared libraries: libnss3.so.1d" issue

After GNU/Linux OS upgrade (at least with Fedora), google-chrome may be broken, complaining about missing libnss3.so.1d library.
To fix this issue:
 - ensure you have installed nss v3.xx (corresponding to your architecture)
 - create a symbolic link to corresponding library in the google-chrome main directory, usually:
ln -s /usr/lib64/libssl3.so /opt/google/chrome/libssl3.so.1d

There is some other needed symbolic links; if you have same kind of issue for others libraries, you can fix them the same way.

Anyway, at worse, if you don't want to fix it manually, you can reinstall google-chrome and reinstall it:
yum remove google-chrome-stable
yum install google-chrome-stable

Upgrade GNU/Linux Fedora from 10 to 11, 12, 13 and finally 14

To upgrade GNU/Linux Fedora from 10 to 11, 12, 13 and finally 14, there is no problem.
Although the way to upgrade is
the same for legacy End Of Life (EOF) Fedora versions (until 10 included), and for Fedora 11; it is easier from Fedora 12 with new yum options --releasever and distro-sync.

The principle is globally the same when upgrading:
- from Fedora core N to Fedora core N+1 (see this post)
- from Fedora 8 to 9, then 10 (see this post)
- from Fedora core 6 to Fedora 7 then 8 (see this post).

In addition, the recommendations of Fedora project have greatly evolved and are complete.

Ensure there is no dependencies problem like explained into this post.

Then, you should perform a great configuration files merging campaign to ensure having the up to date functionalities while keeping your own specific configuration (globally the XXX.conf and XXX.conf.rpmnew files).