Pidgin silently crashed with SIGSEGV due to pn_peer_call_free() in libmsn-pecan

[druisan]

Binary package hint: pidgin

When I am working/speaking with Pidgin, it closes automatically.
This began when I used ubuntu 9.04. I know much people who have got this issue too.

Thanks.

ProblemType: Bug
Architecture: i386
Date: Sun Nov 15 11:21:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
NonfreeKernelModules: nvidia
Package: pidgin 1:2.6.2-1ubuntu7
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: pidgin
Uname: Linux 2.6.31-14-generic i686

[Gary Alexander (alexanderg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Specifically, what protocol(s) are you using to connect with, and if you run pidgin from a terminal do you get any output?

[Sheng Yang (yasker)]

I have used -d for debug info, but still can't get anything in the console except a Segment fault...

[Sheng Yang (yasker)]

Of course, I means anything useful... The line before Segment Fault is a something like "dns: nothing to do", it happened from time to time, I think maybe there is no relationship.

[Sheng Yang (yasker)]

Got this in dmesg.

[246218.977989] pidgin[26667] general protection ip:7fac1c174c98 sp:7fff9db29340 error:0 in libglib-2.0.so.0.2200.2[7fac1c13b000+c5000]
[252150.979260] pidgin[28296] general protection ip:7f89e7610c98 sp:7fff28981eb0 error:0 in libglib-2.0.so.0.2200.2[7f89e75d7000+c5000]

[Sheng Yang (yasker)]

One more word: I am using kubuntu 9.10.

The pidgin issue highly affect the daily usage, please consider to take a look at it... Or could I provide more info?

Thanks!

[Sheng Yang (yasker)]

OK, I can't bear this bug any more....

So here is the backtrace from gdb.

#0 0x00007ffff4e07c98 in g_list_remove () from /lib/libglib-2.0.so.0
#1 0x00007fffe27b0ec5 in pn_peer_call_free () from /usr/lib/purple-2/libmsn-pecan.so
#2 0x00007fffe27b0f25 in pn_peer_call_unref () from /usr/lib/purple-2/libmsn-pecan.so
#3 0x00007fffe27b0fa8 in ?? () from /usr/lib/purple-2/libmsn-pecan.so
#4 0x00007ffff4e0a2cb in ?? () from /lib/libglib-2.0.so.0
#5 0x00007ffff4e09bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#6 0x00007ffff4e0d588 in ?? () from /lib/libglib-2.0.so.0
#7 0x00007ffff4e0d9e5 in g_main_loop_run () from /lib/libglib-2.0.so.0
#8 0x00007ffff699b177 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#9 0x00000000004858bf in main (argc=1, argv=0x7fffffffe1a8) at /build/buildd/pidgin-2.6.2/./pidgin/gtkmain.c:915

Then I found this bug report when googling, but they "mark it as fixed"....:
http://code.google.com/p/msn-pecan/issues/detail?id=202

[Sheng Yang (yasker)]

I think the bug could be marked as Medium priority, due to it randomly crash pidgin(almost every hour for me) and heavily affect the daily usage. I didn't find another way to trigger this bug. I've tried logout/login, still OK...

[Sheng Yang (yasker)]

Now it crashed with start up. No change for any input. Suggest mark it as Critical.

#0 0x00007fffe27970bf in ?? () from /usr/lib/purple-2/libmsn-pecan.so
#1 0x00007ffff5c58791 in purple_accounts_restore_current_statuses () at /build/buildd/pidgin-2.6.2/./libpurple/account.c:2730
#2 0x0000000000485a28 in main (argc=1, argv=0x7fffffffe198) at /build/buildd/pidgin-2.6.2/./pidgin/gtkmain.c:895

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version. Thanks in advance

[druisan (druisan)]

I got this problem fixed when I disabled Pidgin's sound. Now it works perfectly

[druisan (druisan)]

This bug got fixed in newest Ubuntu versions.