Red Hat Bugzilla – Bug 456619
https URLs clicked in thunderbird-1.5 do not initiate seamonkey properly
Last modified: 2009-08-11 06:51:31 EDT
Description of problem:
1- set default browser to seamonkey
2- upgrade seamonkey to 1.0.9-24.el4, (requires nss-188.8.131.52-3.el4)
3- start thunderbird
4- view an email with a https URL
5- click it
This document connot be displayed unless you install the Personal Security
Manager (PSM). Download and install PSM and try again, or contact your system
Version-Release number of selected component (if applicable):
https page should load
I can't reproduce this with evo28 & new seamonkey/nss packages
or with thunderbird and old seamonkey/seamonkey-nss packages
Additionally, clicking a URL in thunderbird with ff3 set as the default browser
does not open the link in ff3.
kengert identified the problem:
<kengert> when thunderbird starts seamonkey, it does so with an LD_LIBRARY_PATH
that includes the nss libraries that are shipped with thunderbird
<kengert> when seamonkey starts up, it might see the libs from thunderbird,
instead of the ones from seamonkey (which are probably later in the path)
<kengert> then there might be some incompatibility between libs
<kengert> let me try to remove the nspr and nss libs shipped with thunderbird ,
which should work fine
<kengert> my test is successful. after having moved the nspr/nss libs away, the
test case can load the https page
Note, https links work if seamonkey is already up and running. So until we have
a fix, users can workaround the issue by launching seamonkey before they click
on an https link in thunderbird.
I can't set the rhel-4.7.z flag
The fix is to change thunderbird to no longer ship an internal NSPR/NSS, but
link against the system packages.
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.
Resolving as a dupe of bug 456193, which already got acks.
Both SeaMonkey and Firefox experience the same problem, a single fix to thunderbird will resolve both problems.
*** This bug has been marked as a duplicate of bug 456193 ***