Bug 637181 – empathy-2.32.2: request_channel_async: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 637181 - empathy-2.32.2: request_channel_async: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)


Summary:	empathy-2.32.2: request_channel_async: Process /usr/bin/empathy was killed by...


Status:	RESOLVED OBSOLETE

Product:	empathy
Classification:	Core
Component:	General
Version:	2.32.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	empathy-maint
QA Contact:	empathy-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-12-13 20:27 UTC by Brian Pepple
Modified:	2010-12-14 12:07 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Backtrace (35.62 KB, text/plain) 2010-12-13 20:27 UTC, Brian Pepple	Details

Description Brian Pepple 2010-12-13 20:27:38 UTC

Created attachment 176363 [details]
Backtrace

abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: empathy
component: empathy
crash_function: request_channel_async
executable: /usr/bin/empathy
kernel: 2.6.35.6-48.fc14.x86_64
package: empathy-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: doing nothing whatsoever... it just crashed
time: 1291347394
uid: 500

Comment 1 Fabio Durán Verdugo 2010-12-14 04:38:19 UTC

paste here the attach backtrace

Core was generated by `empathy'.
Program terminated with signal 11, Segmentation fault.

+ Trace 225123

Thread 1 (Thread 6620)

#0 request_channel_async
at account-channel-request.c line 959
#1 empathy_dispatcher_chat_with_contact_id
at empathy-dispatcher.c line 529
#2 individual_view_row_activated
at empathy-individual-view.c line 929
#3 g_closure_invoke
at gclosure.c line 766
#4 signal_emit_unlocked_R
at gsignal.c line 3290
#5 g_signal_emit_valist
at gsignal.c line 2983
#6 g_signal_emit
at gsignal.c line 3040
#7 gtk_tree_view_button_press
at gtktreeview.c line 2876
#8 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 86
#9 g_closure_invoke
at gclosure.c line 766
#10 signal_emit_unlocked_R
at gsignal.c line 3290
#11 g_signal_emit_valist
at gsignal.c line 2993
#12 g_signal_emit
at gsignal.c line 3040
#13 gtk_widget_event_internal
at gtkwidget.c line 4992
#14 IA__gtk_propagate_event
at gtkmain.c line 2460
#15 IA__gtk_main_do_event
at gtkmain.c line 1665
#16 gdk_event_dispatch
at gdkevents-x11.c line 2377
#17 g_main_dispatch
at gmain.c line 2149
#18 g_main_context_dispatch
at gmain.c line 2702
#19 g_main_context_iterate
at gmain.c line 2780
#20 g_main_loop_run
at gmain.c line 2988
#21 IA__gtk_main
at gtkmain.c line 1237
#22 main
at empathy.c line 550

Comment 2 Guillaume Desmottes 2010-12-14 12:07:39 UTC

I suspect this is a consequence of the old contact objects staying around we recently fixed. Please re-open if you manage to reproduce using a recent release.