Bug 663540 – crash after inviting someone into a group chat (from a 1:1 chat)

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 663540 - crash after inviting someone into a group chat (from a 1:1 chat)


Summary:	crash after inviting someone into a group chat (from a 1:1 chat)


Status:	RESOLVED OBSOLETE

Product:	empathy
Classification:	Core
Component:	Multi User Chat
Version:	3.2.x
Hardware:	Other Linux

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

URL:
Whiteboard:

Depends on:	663694
Blocks:

Reported:	2011-11-07 04:53 UTC by Danielle Madeley
Modified:	2012-09-13 09:18 UTC

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

Description Danielle Madeley 2011-11-07 04:53:01 UTC

Crashed a little after inviting someone into a group chat (from a 1:1 chat). Dialog had been closed by this point.

+ Trace 229007

#0 empathy_live_search_match_words
at empathy-live-search.c line 234
#1 empathy_individual_match_string
at empathy-ui-utils.c line 2059
#2 filter_func
at empathy-contact-chooser.c line 175
#3 individual_view_filter_visible_func
#4 ??
from /usr/lib/libgtk-3.so.0
#5 ??
from /usr/lib/libgtk-3.so.0
#6 ??
from /usr/lib/libgtk-3.so.0
#7 g_closure_invoke
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#8 ??
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#10 g_signal_emit
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#11 gtk_tree_model_row_changed
from /usr/lib/libgtk-3.so.0
#12 gtk_tree_store_set_valist
from /usr/lib/libgtk-3.so.0
#13 gtk_tree_store_set
from /usr/lib/libgtk-3.so.0
#14 individual_store_contact_update
at empathy-individual-store.c line 729
#15 individual_store_contact_updated_cb
at empathy-individual-store.c line 798
#16 g_cclosure_marshal_VOID__PARAM
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#18 ??
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#21 ??
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#22 ??
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#23 g_object_notify
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#24 contact_set_client_types
at empathy-contact.c line 1562
#25 tp_contact_notify_cb
at empathy-contact.c line 176
#26 g_cclosure_marshal_VOID__PARAM
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#28 ??
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#31 ??
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#32 ??
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#33 g_object_notify
from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#34 ??
from /usr/lib/libtelepathy-glib.so.0
#35 ??
from /usr/lib/libtelepathy-glib.so.0
#36 ??
from /usr/lib/libtelepathy-glib.so.0
#37 ??
from /lib/i386-linux-gnu/libglib-2.0.so.0
#38 g_main_context_dispatch
from /lib/i386-linux-gnu/libglib-2.0.so.0
#39 ??
from /lib/i386-linux-gnu/libglib-2.0.so.0
#40 g_main_loop_run
from /lib/i386-linux-gnu/libglib-2.0.so.0
#41 gtk_main
from /usr/lib/libgtk-3.so.0
#42 ??
from /usr/lib/libgtk-3.so.0
#43 g_application_run
from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#44 main
at empathy-chat.c line 160

Comment 1 Guillaume Desmottes 2011-11-07 13:27:33 UTC

Looks like the EmpathyInvidiualStore created in the contact chooser survived it. I did some tests and it seems to always be destroyed when closing the window here.

Comment 2 Guillaume Desmottes 2011-11-09 13:41:49 UTC

I bet that's because of bug #663694. I experienced similar issues when working on bug #663387.

Let's retry once it has been fixed.

Comment 3 Guillaume Desmottes 2012-09-13 09:18:12 UTC

Looks like this has been fixed; closing.