Bug 436631

I have reported this upstream as well:

http://developer.pidgin.im/ticket/5163

I think it's more to do with changing network connections. I've seen Pidgin
crash shortly after pulling an Ethernet connection (and then re-plugging or
moving to wireless), or sometimes not reconnecting after an interface has come up.

I believe this may be due to the jabber protocol and timeouts of connections. I
have pidgin-2.4.0-1.fc8 and after I captured a core, get this backtrace for the
offending thread:

#0  0x00110402 in __kernel_vsyscall ()
No symbol table info available.
#1  0x00582690 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
	resultvar = <value optimized out>
	pid = 7004148
	selftid = 4646
#2  0x00583f91 in abort () at abort.c:88
	act = {__sigaction_handler = {sa_handler = 0, sa_sigaction = 0}, 
  sa_mask = {__val = {0 <repeats 23 times>, 6024308, 694, 3216882204, 
      6411252, 6411266, 6014068, 2, 164440512, 694}}, sa_flags = 7005536, 
  sa_restorer = 0x2b6}
	sigs = {__val = {32, 0 <repeats 31 times>}}
#3  0x080c0e6b in sighandler (sig=11) at gtkmain.c:220
No locals.
#4  <signal handler called>
No symbol table info available.
#5  jabber_pong_timeout (gc=0xa267fb0) at jabber.c:402
	js = (JabberStream *) 0x0
#6  0x00215966 in g_timeout_dispatch (source=0xa26db18, callback=0, 
    user_data=0xa267fb0) at gmain.c:3488
No locals.
#7  0x002151ac in IA__g_main_context_dispatch (context=0x9ceeff8)
    at gmain.c:2061
No locals.
#8  0x002185ef in g_main_context_iterate (context=0x9ceeff8, block=1, 
    dispatch=1, self=0x9cce238) at gmain.c:2694
	got_ownership = <value optimized out>
	max_priority = 2147483647
	timeout = 7954
	some_ready = 1
	nfds = <value optimized out>
	allocated_nfds = <value optimized out>
	fds = (GPollFD *) 0xa0fd388
	__PRETTY_FUNCTION__ = "g_main_context_iterate"
#9  0x00218999 in IA__g_main_loop_run (loop=0xa036308) at gmain.c:2898
	got_ownership = 9593664
	self = (GThread *) 0x9cce238
	__PRETTY_FUNCTION__ = "IA__g_main_loop_run"
#10 0x03e917ee in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#11 0x080c16ba in main (argc=1, argv=0xbfbe01b4) at gtkmain.c:887
	display = <value optimized out>
	opt_help = <value optimized out>
	opt_login = 0
	opt_nologin = 0
	opt_version = <value optimized out>
	opt_si = 1
	opt_config_dir_arg = 0x0
	opt_login_arg = 0x0
	opt_session_arg = 0x0
	accounts = <value optimized out>
	sig_indx = <value optimized out>
	sigset = {__val = {91143, 0 <repeats 31 times>}}
	prev_sig_disp = <value optimized out>
	errmsg =
"\000\000\000\000±éT\000\000\000\000\000Ký½¿À_U\000Àx¢\000 3¥\000¼὿À_U\000\003\000\000\000À\004E\000D὿åêT\000\b\000\000\000\034\000\000\000À_U\000Xý½¿\204kT\000ð\236ó·à\236ó·\f\000\000\000ædT\000\001\000\000\000°\"ô·\230Òó·\000\000\000\000\000\000\000\0000
Æ\000T⽿¶\201T\000(ý½¿±éT\000\004\000\000\000PåtdKý½¿Dý½¿@ý½¿¤eU\000À_U\000\004
\000\000\000P4¥\000¼὿åêT\000\b\000\000\000$\000\000\000À_U\000Xý½¿\204kT\000Ì\236ó·¸\236ó·"...
	segfault_message_tmp = <value optimized out>
	error = (GError *) 0x0
	opt = <value optimized out>
	gui_check = <value optimized out>
	debug_enabled = <value optimized out>
	migration_failed = <value optimized out>
	active_accounts = <value optimized out>
	long_options = {{name = 0x810884a "config", has_arg = 1, flag = 0x0, 
    val = 99}, {name = 0x80f8b39 "debug", has_arg = 0, flag = 0x0, 
    val = 100}, {name = 0x80fb8e3 "help", has_arg = 0, flag = 0x0, 
    val = 104}, {name = 0x80f8df1 "login", has_arg = 2, flag = 0x0, 
    val = 108}, {name = 0x8104ed4 "multiple", has_arg = 0, flag = 0x0, 
    val = 109}, {name = 0x8104edd "nologin", has_arg = 0, flag = 0x0, 
    val = 110}, {name = 0x8108840 "session", has_arg = 1, flag = 0x0, 
    val = 115}, {name = 0x80fd620 "version", has_arg = 0, flag = 0x0, 
    val = 118}, {name = 0x8108853 "display", has_arg = 1, flag = 0x0, 
    val = 68}, {name = 0x8104ee5 "sync", has_arg = 0, flag = 0x0, val = 83}, {
    name = 0x0, has_arg = 0, flag = 0x0, val = 0}}

I believe the offending call is in frame #5 and that there is an attempt to free
a NULL pointer (pidgin SIGSEGV's).

Yes, it is related to the XMPP ping timeouts. No, it's not as simple as
dereferencing a NULL pointer. See http://developer.pidgin.im/ticket/4814 for the
upstream ticket.

*** Bug 438607 has been marked as a duplicate of this bug. ***

pidgin-2.4.1-1.fc8 has been submitted as an update for Fedora 8

pidgin-2.4.1-1.fc7 has been pushed to the Fedora 7 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update pidgin'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F7/FEDORA-2008-2846

The update appears good. Same laptop and network connection as the original bug
report, latest F8 updates applied as of 2008-03-03 20:00 PST. I have left Pidgin
logged in and running, let the laptop suspend overnight on it's own and waken it
up - Pidgin remains (re)connected and running as expected and desired. Thanks!

This update works for me on f8

If the F8 update fixes/do not fixes the bug for, you can comment on:

https://admin.fedoraproject.org/updates/F8/FEDORA-2008-2863

pidgin-2.4.1-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

pidgin-2.4.1-1.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.