Bug 918816

Summary: 3.2 crashes on start
Product: [Fedora] Fedora Reporter: Kevin Fenzi <kevin>
Component: bitlbeeAssignee: Robert Scheck <redhat-bugzilla>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: mcepl, mcepl, pp, redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://bugs.bitlbee.org/bitlbee/ticket/1040
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-25 13:10:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kevin Fenzi 2013-03-07 00:21:45 UTC 
Upgraded from bitlbee-3.0.5-1.fc18 to 3.2-1.fc18, but it keeps crashing over and over: 

Mar  6 17:18:28 dworkin bitlbee[11977]: *** glibc detected *** /usr/sbin/bitlbee: munmap_chunk(): in
valid pointer: 0x00007fdef88f61d8 ***
Mar  6 17:18:28 dworkin bitlbee[11977]: ======= Backtrace: =========
Mar  6 17:18:28 dworkin bitlbee[11977]: /lib64/libc.so.6(+0x31fdc7b776)[0x7fdef55f9776]
Mar  6 17:18:28 dworkin bitlbee[11977]: /lib64/libglib-2.0.so.0(g_free+0xf)[0x7fdef71e779f]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(ssl_disconnect+0x1b)[0x7fdef7b1a8fb]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(+0x3ff58)[0x7fdef7b2af58]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(imc_logout+0xb0)[0x7fdef7b1eba0]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(sasl_pkt_result+0x9b)[0x7fdef7b3076b]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(xt_handle+0xd4)[0x7fdef7b1b3e4]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(xt_handle+0x57)[0x7fdef7b1b367]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(+0x3cd95)[0x7fdef7b27d95]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(+0x27a75)[0x7fdef7b12a75]
Mar  6 17:18:28 dworkin bitlbee[11977]: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7fd
ef71e1a55]
Mar  6 17:18:28 dworkin bitlbee[11977]: /lib64/libglib-2.0.so.0(+0x31bba47d88)[0x7fdef71e1d88]
Mar  6 17:18:28 dworkin bitlbee[11977]: /lib64/libglib-2.0.so.0(g_main_loop_run+0x72)[0x7fdef71e2182
]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(main+0x24f)[0x7fdef7afe12f]
Mar  6 17:18:28 dworkin bitlbee[11977]: /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fdef559fa05]
Mar  6 17:18:28 dworkin bitlbee[11977]: /usr/sbin/bitlbee(+0x13695)[0x7fdef7afe695]
Mar  6 17:18:28 dworkin bitlbee[11977]: ======= Memory map: ========

Downgrading back to 3.0.5 and everything seems to work. 

Happy to try and gather more info...
Comment 1 Pekka Pietikäinen 2013-03-25 12:58:10 UTC 
Reported upstream. Smells like it's something that only happens when bitlbee is linked against NSS (vs. say OpenSSL). MSN and XMPP (Facebook) in use here.
Comment 2 Robert Scheck 2013-03-25 13:10:23 UTC 
This issue is IMHO specific to NSS, I can not see any of these issues once
I link BitlBee against OpenSSL.

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