The seamonkey-1.0.8-x (critical) update prevents evolution from starting. The following error occurs: (evolution:32071): evolution-smime-WARNING **: Failed all methods for initializing NSS Trying to build evolution from the SRPM also does not work as the path for nspr (mozilla 37:1.8) is not the same as the path for nspr (seamonkey 1.0.8). Using the patch attached to this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202453 I was able to start Evolution building ... whether it fixes this bug, I will report when it finishes.
rebuilding evolution did not help, the RPM produced built against seamonkey 1.0.8 is identical to the one produced against mozilla
There is a fix that works as a work around until another solution is done, which list to create this symbolic link: cd /usr/lib ln -s firefox-1.5.0.10/libfreeb13.so . Having libfreeb13.so in /usr/lib allows evolution to start ... removing it prevents it from starting. This fix is from the centos bugs tracker and mailing list: http://bugs.centos.org/view.php?id=1694
I have exactly the same issue. After the latest rhn update evolution failed to start. I did as suggested by Johnny (thanks), and got evolution to start. This is very urgent, as I am sure many other people are running into the same issue, and are completely lost as I!
OK ... that file name should have a "lowercase L" (l) not a one (1) ... cd /usr/lib ln -s firefox-1.5.0.10/libfreebl3.so
*** Bug 230048 has been marked as a duplicate of this bug. ***
libfreebl3.so is new to NSS3.11 and it is dlopened by libsoftokn3.so. Therefore the seamonkey-nss library should be shipping libfreebl3.so in /usr/lib (and not in the seamonkey main rpm). We are therefore respinning seamonkey packages to replace the current erratum packages and will expidite them through QE and release engineering.
FYI: This bug also breaks gaim
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
*** Bug 230111 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2007-0077.html
*** Bug 230070 has been marked as a duplicate of this bug. ***