Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230070 - Broke NSS ABI - seamonkey security errata
Summary: Broke NSS ABI - seamonkey security errata
Status: CLOSED DUPLICATE of bug 229987
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: seamonkey
Version: 4.4
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Gecko Maintainer
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-26 14:24 UTC by daryl herzmann
Modified: 2007-11-17 01:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-03-09 15:27:20 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description daryl herzmann 2007-02-26 14:24:55 UTC
Some recent update has hosed Gaim.  It will now crash on connect to Jabber TLS
servers.  Been able to reproduce here on fully updated EL4 machines.

Perhaps the seamonkey or firefox updates messed up TLS for Gaim?

Comment 1 Warren Togami 2007-02-26 15:10:40 UTC
Could you please figure out which update exactly caused this failure?

Please also install relevant debuginfo and attach gdb tracebacks of the crash here.

Comment 2 daryl herzmann 2007-02-26 15:21:24 UTC

Starting with a fresh EL4.4 box.  gaim-1.5.0-12.el4 works fine.

Update seamonkey, gaim crashes on connect.

I'm efforting gdb trace now. Will take me a bit to get setup.


Comment 3 daryl herzmann 2007-02-26 15:40:17 UTC
I installed gaim-debuginfo and ran gaim like so:

gdb gaim

(gdb) bt full
#0  0x009b85b5 in PR_Write () from /usr/lib/
No symbol table info available.
#1  0x0077a169 in ssl_nss_write (gsc=0x8af0e48, data=0x8007375, len=134247285)
    at ssl-nss.c:262
        nss_data = (GaimSslNssData *) 0x8aead28
#2  0x00d7af7a in gaim_ssl_write (gsc=0x8af0e48, data=0x8b18cc8, len=67)
    at sslconn.c:223
        __PRETTY_FUNCTION__ = "gaim_ssl_write"
#3  0x0065de1b in jabber_send_raw (js=0x8ae1df0,
    data=0x8b18cc8 "<presence type='unavailable'><status>Logged
out</status></presence>", len=67) at jabber.c:205
        ret = Variable "ret" is not available.

hopefully that is useful

Comment 4 Jack Neely 2007-02-26 15:46:09 UTC
Yes...the security updates to libnspr seem to have altered teh ABI. stuff.

Comment 5 Philip Durbin 2007-02-26 17:00:44 UTC
Rolling back to the previous versions of seamonkey-nss and seamonkey-nspr (with
all those dire advisories) allowed me to use Jabber with Gaim again:

rpm -Uvh --oldpackage seamonkey-nss-1.0.7-0.1.el4.i386.rpm


Comment 6 daryl herzmann 2007-02-26 21:08:00 UTC

Sorry for the noise, but Bug 229987 seems to indicate an errata is coming soon.
 Will this issue be resolved as well?


Comment 7 Martin Stransky 2007-02-26 21:11:35 UTC
It should be.

Comment 8 daryl herzmann 2007-02-26 22:23:21 UTC
Just applied seamonkey errata.  Looks good :)

Comment 9 Jack Neely 2007-02-26 22:44:54 UTC
I've tested and confirmed that this particular issue is solved.  However, in our
rush to fix things no one noticed that RHEL 3 suffers the same bugs.  I've created

which is a clone of Bug #229987 for RHEL 3.

Comment 10 Matěj Cepl 2007-02-27 22:36:23 UTC
But this bug should be resolved, right?

Comment 11 Philip Durbin 2007-02-28 14:53:55 UTC
It's probably safe to resolve this bug.  Gaim and Evolution have both worked
fine on my Red Hat Desktop since I installed seamonkey-nss-1.0.8-0.2.el4 and
seamonkey-nspr-1.0.8-0.2.el4 per


Comment 12 Jack Neely 2007-02-28 16:11:40 UTC
Against RHEL 4 this bug has been resolved.

However, this still exists for RHEL 3:  See Bug #230158

Comment 14 daryl herzmann 2007-03-08 22:32:26 UTC
Why has't EL3 been fixed yet?  I just verified that Gaim doesn't work on EL3 as
I reported in this bug for EL4.

Comment 15 Matěj Cepl 2007-03-09 15:27:20 UTC

*** This bug has been marked as a duplicate of 229987 ***

Note You need to log in before you can comment on or make changes to this bug.