Evolution won't start after upgrade to Hardy (8.04)

[Jon Warbrick]

After upgrading (from 7.04 to 7.10, and then 7.10 to 8.04 using the update manager) evolution no longer starts:

 $ evolution

 (evolution:11300): evolution-smime-WARNING **: Failed all methods for initializing NSS

 (evolution:11300): camel-WARNING **: Failed to initialize NSS

It may be significant that Psi is also failing to login to Google (though worked before the upgrade), reporting 'Cannot login: SSL is enabled but no SSL/TLS (plugin) support is available'.

$ lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04
$ apt-cache policy evolution
evolution:
  Installed: 2.22.2-0ubuntu1.3
  Candidate: 2.22.2-0ubuntu1.3
  Version table:
 *** 2.22.2-0ubuntu1.3 0
        500 http://gb.archive.ubuntu.com hardy-updates/main Packages
        500 http://archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     2.22.2-0ubuntu1.2 0
        500 http://security.ubuntu.com hardy-security/main Packages
     2.22.1-0ubuntu3 0
        500 http://gb.archive.ubuntu.com hardy/main Packages
$ apt-cache policy psi
psi:
  Installed: 0.11-3
  Candidate: 0.11-3
  Version table:
 *** 0.11-3 0
        500 http://gb.archive.ubuntu.com hardy/universe Packages
        100 /var/lib/dpkg/status

[Jon Warbrick (jw35)]

The Psi problem turns out to be a red-herring - installing libqca2-plugin-ossl (as per Bug #188699) gets Psi working again. This is probably a Psi bug, but nothing to do with Evolution.

[Jon Warbrick (jw35)]

Note that this is not a case of Bug #236218 - I have libnss3-0d installed:

$ apt-cache policy libnss3-0d
libnss3-0d:
  Installed: 3.12.0.2+1.9-0ubuntu0.8.04.1
  Candidate: 3.12.0.2+1.9-0ubuntu0.8.04.1
  Version table:
 *** 3.12.0.2+1.9-0ubuntu0.8.04.1 0
        500 http://gb.archive.ubuntu.com hardy-updates/main Packages
        500 http://archive.ubuntu.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     3.12.0~beta3-0ubuntu1 0
        500 http://gb.archive.ubuntu.com hardy/main Packages

Nor does it appear to be directly related to older bugs which could be worked around by

  LD_LIBRARY_PATH=/usr/lib/firefox

I have a second machine that has had much the same history (though somewhat different package lists) on which Evolution works fine. I can't see any obvious differences in the packages installed.

[Pedro Villavicencio (pedro)]

thanks for your report, are you using an IMAP account? can you get a log of CAMEL_DEBUG=all evolution >& evo.log and upload that file to the report? thanks.

[Jon Warbrick (jw35)]

> thanks for your report, are you using an IMAP account?

Yes, and it will be an SSL/TLS-secured one, though I can't remember exactly how it must be configured.

> can you get a log of CAMEL_DEBUG=all evolution >& evo.log and upload that file to the report?

Done, though it doesn't seem to contain anything other than the two error messages already quoted...

[Jon Warbrick (jw35)]

Hm, comparison of strace output on the working and failing systems shows the failing one accessing /usr/local/lib/libsqlite3.so.0 shortly before everything goes wrong. At the same point the working system accesses /usr/lib/libsqlite3.so.0. Moving the /usr/local/ SQLite libraries out of the way seems to fix the problem.

I don't know where the SQLite libraries in /usr/local/ came from, but they must have been from a manual installation of something at some time in the past, and I'm guessing they were in some way incompatible with Evolution and were knocking it into a spin.

So, use error and not an Ubuntu bug. Apologies for wasting anyone's time.

[Sebastien Bacher (seb128)]

closing the bug since that's not one but an user installation error