pidgin crashed with SIGSEGV upon clicking on Facebook messages (notifications) in Pidgin

[William Bohn]

Binary package hint: pidgin

While using the additional package that allows Pidgin to use Facebook's information, I opened a "mail" (Facebook notification) message, and the link made Pidgin crash. No web browser was open at the time. Expected to go to open a web browser window and go to link.

Ubuntu 9.04
pidgin 1:2.5.5-1ubuntu5

ProblemType: Crash
Architecture: i386
Disassembly: 0xb785458d:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.5-1ubuntu5
ProcCmdline: pidgin
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
Stacktrace: #0 0xb785458d in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: pidgin crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[William Bohn (shambler)]

I'm having difficulty reproducing the crash while doing backtracing now.

Is it possible to get that backtrace using a core dump or something else? (Apologies if I don't know what I'm talking about here - it's been awhile since I programmed)

[Hew (hew)]

Thanks for your backtrace. Unfortunately it is missing debug symbols. You will need to install libglib2.0-0-dbg and libgtk2.0-0-dbg (or -dbgsym variants) before obtaining the backtrace. Thanks again for your help with this bug!

[William Bohn (shambler)]

Okay, I've managed to finally get it to crash on my again. Here's the backtrace with (hopefully) the correct debugging symbols.
I hope this helps!

[Hew (hew)]

Thanks for the new backtrace, but this looks like a different crash, which I think needs libc6-i686-dbgsym for that (see the lines saying "No symbol table info available"). Did this crash occur with a different action?

Upstream has a new version 1.50, so it's probably worth testing with this to see if the crash still persists.

[William Bohn (shambler)]

Still crashing. Attached is another backtrace- and no, I'm not doing anything else. I hope this helps.

[Hew (hew)]

Thanks for your persistent effort William, this trace looks complete! Marked as triaged so a developer can have a look.

[Jonathan Davies (jpds)]

Eion: Could you take a look at the backtrace and see if it's fixed?

[BigBrownChunx (eion)]

This is related to http://code.google.com/p/pidgin-facebookchat/issues/detail?id=377 upstream.

From what I can tell, its a bug in Pidgin, but we haven't tracked down the exact cause as all the backtraces relate to the display of notifications, rather than the code in pidgin-facebookchat which adds them to the list.