pidgin SIGSEGV

Bug #665736 reported by Marc MERLIN
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: pidgin

It crashes by itself when I'm not touching it (some time after launch)

Starting program: /usr/bin/pidgin
[Thread debugging using libthread_db enabled]
warning: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.7" does not match "/usr/lib/libxml2.so.2" (CRC mismatch).

[New Thread 0xb5e2db70 (LWP 15170)]
(Pidgin:15167): pidgin-libnotify-plugin-DEBUG: Successfully wrote blacklist file to /home/merlin/.config/indicators/messages/applications-blacklist/pidgin-libnotify
[New Thread 0xafc3cb70 (LWP 15191)]
[New Thread 0xaf27bb70 (LWP 15192)]
[New Thread 0xae4bcb70 (LWP 15193)]
[New Thread 0xadcbbb70 (LWP 15194)]
[New Thread 0xad4bab70 (LWP 15195)]
[New Thread 0xaccb9b70 (LWP 15196)]

Program received signal SIGSEGV, Segmentation fault.
0xb76abd8c in ?? () from /usr/lib/libpurple.so.0
(gdb) bt
#0 0xb76abd8c in ?? () from /usr/lib/libpurple.so.0
#1 0xb7ec23cc in marshal_VOID__MINIOBJECT (closure=0x8f6b5e8,
    return_value=0x0, n_param_values=2, param_values=0x97e2d90,
    invocation_hint=0xbfffce20, marshal_data=0x0) at gstbus.c:133
#2 0xb782c412 in g_closure_invoke (closure=0x8f6b5e8, return_value=0x0,
    n_param_values=2, param_values=0x97e2d90, invocation_hint=0xbfffce20)
    at /build/buildd/glib2.0-2.26.0/gobject/gclosure.c:766
#3 0xb7842595 in signal_emit_unlocked_R (node=<value optimized out>,
    detail=<value optimized out>, instance=0x86a3aa8, emission_return=0x0,
    instance_and_params=0x97e2d90)
    at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c:3252
#4 0xb78439bc in g_signal_emit_valist (instance=0x86a3aa8, signal_id=121,
    detail=638, var_args=0xbfffcff0 "¨:j\b")
    at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c:2983
#5 0xb7843e62 in g_signal_emit (instance=0x86a3aa8, signal_id=121, detail=638)
    at /build/buildd/glib2.0-2.26.0/gobject/gsignal.c:3040
#6 0xb7ec0911 in gst_bus_async_signal_func (bus=0x86a3aa8, message=0x97d5420,
    data=0x0) at gstbus.c:1099
#7 0xb7ec1915 in gst_bus_source_dispatch (source=0x90c51a8,
    callback=0xb7ec0870 <gst_bus_async_signal_func>, user_data=0x0)
    at gstbus.c:760
#8 0xb7789855 in g_main_dispatch (context=0x8123898)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2149
#9 g_main_context_dispatch (context=0x8123898)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2702
#10 0xb778d668 in g_main_context_iterate (context=0x8123898,
    block=<value optimized out>, dispatch=1, self=0x811f008)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2780
#11 0xb778dba7 in g_main_loop_run (loop=0x8edab28)
    at /build/buildd/glib2.0-2.26.0/glib/gmain.c:2988
#12 0xb7a9f1d9 in IA__gtk_main ()
    at /build/buildd/gtk+2.0-2.22.0/gtk/gtkmain.c:1237
#13 0x080c6ee1 in main ()

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: pidgin 1:2.7.3-1ubuntu3
Uname: Linux 2.6.34.1-core2smp-1khznohz-preempt-notcks-noide-hm64-20100724 i686
Architecture: i386
Date: Sat Oct 23 16:05:59 2010
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.ISO-8859-1
 SHELL=/bin/bash
SourcePackage: pidgin

Revision history for this message
Marc MERLIN (marc-soft) wrote :
Revision history for this message
Charlie Kravetz (charlie-tca) wrote :

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.

Changed in pidgin (Ubuntu):
status: New → Incomplete
Revision history for this message
Charlie Kravetz (charlie-tca) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Marc MERLIN (marc-soft) wrote :

I'll try to get this again, but I can't get it on command.
But to be clear, what is wrong with the backtrace I originally attached?

Revision history for this message
Charlie Kravetz (charlie-tca) wrote :

Is that included in the original report? If that is a complete gdb trace, it looks good. The problem with including it that way is I could not determine if it was complete, or a partial trace copied from one of the log files. It is much better to attach such things as separate plain text files.

I will go ahead and mark this confirmed based on that trace then. Thanks so much for letting us know.

Revision history for this message
Charlie Kravetz (charlie-tca) wrote :

Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. NOTE: Stacktrace is included in the description. Thanks for taking the time to make Ubuntu better!

Changed in pidgin (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers