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 635813 - empathy-2.32.0.1: magazine_chain_pop_head: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
empathy-2.32.0.1: magazine_chain_pop_head: Process /usr/bin/empathy was kille...
Status: RESOLVED DUPLICATE of bug 631856
Product: empathy
Classification: Core
Component: General
2.32.x
Other Linux
: Normal critical
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2010-11-25 21:41 UTC by Brian Pepple
Modified: 2010-11-26 05:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Backtrace (52.69 KB, text/plain)
2010-11-25 21:41 UTC, Brian Pepple
Details

Description Brian Pepple 2010-11-25 21:41:10 UTC
Created attachment 175279 [details]
Backtrace

abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: empathy
component: empathy
crash_function: magazine_chain_pop_head
executable: /usr/bin/empathy
kernel: 2.6.35.6-48.fc14.x86_64
package: empathy-2.32.0.1-3.fc14
rating: 4
reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1290617551
uid: 500

How to reproduce
-----
1. double click on contact to open window to retrieve offline message
Comment 1 Fabio Durán Verdugo 2010-11-26 05:16:54 UTC
paste here the attach backtrace...


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

Thread 1 (Thread 21615)

  • #0 magazine_chain_pop_head
    at gslice.c line 492
  • #1 thread_memory_magazine1_alloc
    at gslice.c line 795
  • #2 g_slice_alloc
    at gslice.c line 833
  • #3 g_slice_alloc0
    at gslice.c line 854
  • #4 g_type_create_instance
    at gtype.c line 1867
  • #5 g_object_constructor
    at gobject.c line 1597
  • #6 g_object_newv
    at gobject.c line 1381
  • #7 g_object_new
    at gobject.c line 1293
  • #8 empathy_chat_window_new
    at empathy-chat-window.c line 2068
  • #9 empathy_chat_window_present_chat
    at empathy-chat-window.c line 2349
  • #10 process_tp_chat
    at empathy-chat-manager.c line 143
  • #11 tp_chat_ready_cb
    at empathy-chat-manager.c line 199
  • #12 g_closure_invoke
    at gclosure.c line 766
  • #13 signal_emit_unlocked_R
    at gsignal.c line 3252
  • #14 g_signal_emit_valist
    at gsignal.c line 2983
  • #15 g_signal_emit
    at gsignal.c line 3040
  • #16 g_object_dispatch_properties_changed
    at gobject.c line 914
  • #17 g_object_notify_queue_thaw
    at gobjectnotifyqueue.c line 132
  • #18 g_object_notify_by_spec_internal
    at gobject.c line 972
  • #19 g_object_notify
    at gobject.c line 1013
  • #20 get_contact_by_handle_cb
    at empathy-tp-contact-factory.c line 310
  • #21 contacts_context_continue
    at contact.c line 1298
  • #22 contacts_context_idle_continue
    at contact.c line 1330
  • #23 g_main_dispatch
    at gmain.c line 2149
  • #24 g_main_context_dispatch
    at gmain.c line 2702
  • #25 g_main_context_iterate
    at gmain.c line 2780
  • #26 g_main_loop_run
    at gmain.c line 2988
  • #27 IA__gtk_main
    at gtkmain.c line 1237
  • #28 main
    at empathy.c line 550

Comment 2 Fabio Durán Verdugo 2010-11-26 05:19:06 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 631856 ***