pidgin SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
Triaged
|
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/
warning: the debug information found in "/usr/lib/
[New Thread 0xb5e2db70 (LWP 15170)]
(Pidgin:15167): pidgin-
[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/
(gdb) bt
#0 0xb76abd8c in ?? () from /usr/lib/
#1 0xb7ec23cc in marshal_
return_
invocation_
#2 0xb782c412 in g_closure_invoke (closure=0x8f6b5e8, return_value=0x0,
n_param_
at /build/
#3 0xb7842595 in signal_
detail=<value optimized out>, instance=0x86a3aa8, emission_
instance_
at /build/
#4 0xb78439bc in g_signal_
detail=638, var_args=0xbfffcff0 "¨:j\b")
at /build/
#5 0xb7843e62 in g_signal_emit (instance=
at /build/
#6 0xb7ec0911 in gst_bus_
data=0x0) at gstbus.c:1099
#7 0xb7ec1915 in gst_bus_
callback=
at gstbus.c:760
#8 0xb7789855 in g_main_dispatch (context=0x8123898)
at /build/
#9 g_main_
at /build/
#10 0xb778d668 in g_main_
block=<value optimized out>, dispatch=1, self=0x811f008)
at /build/
#11 0xb778dba7 in g_main_loop_run (loop=0x8edab28)
at /build/
#12 0xb7a9f1d9 in IA__gtk_main ()
at /build/
#13 0x080c6ee1 in main ()
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: pidgin 1:2.7.3-1ubuntu3
Uname: Linux 2.6.34.
Architecture: i386
Date: Sat Oct 23 16:05:59 2010
ProcEnviron:
PATH=(custom, no user)
LANG=en_
SHELL=/bin/bash
SourcePackage: pidgin
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/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.