Bug 368794 – crash in Gossip Instant Messenger:

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 368794 - crash in Gossip Instant Messenger:


Summary:	crash in Gossip Instant Messenger:


Status:	RESOLVED DUPLICATE of bug 322110

Product:	gossip
Classification:	Deprecated
Component:	Telepathy
Version:	0.18
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gossip Maintainers
QA Contact:	Gossip Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-01 10:25 UTC by Xavier Claessens
Modified:	2006-11-13 21:50 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Xavier Claessens 2006-11-01 10:25:30 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 42295296 vsize: 0 resident: 42295296 share: 0 rss: 18509824 rss_rlim: 0
CPU usage: start_time: 1162373567 rtime: 0 utime: 249 stime: 0 cutime:226 cstime: 0 timeout: 23 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/local/bin/gossip'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227000144 (LWP 6865)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 81371

Thread 1 (Thread -1227000144 (LWP 6865))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_str_hash
from /usr/lib/libglib-2.0.so.0
#5 g_hash_table_insert
from /usr/lib/libglib-2.0.so.0
#6 telepathy_send_message
at gossip-telepathy.c line 1195
#7 gossip_protocol_send_message
at gossip-protocol.c line 397
#8 gossip_session_send_message
at gossip-session.c line 1207
#9 private_chat_input_key_press_event_cb
at gossip-private-chat.c line 363
#10 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_window_propagate_key_event
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_window_activate_key
from /usr/lib/libgtk-x11-2.0.so.0
#18 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#20 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#24 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#27 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
at gossip-main.c line 201
#0 __kernel_vsyscall

Comment 1 Xavier Claessens 2006-11-01 10:34:53 UTC

Sorry I forgot to say when the crash appear:

If I connect to butterfly and gabble at the same time and I send a msg to a jabber contact gossip crash. If I don't connect to butterfly it works.

Comment 2 Xavier Claessens 2006-11-11 09:40:17 UTC

I think I understand where is the bug. In telepathy_send_message() it sends the message with the priv->account. So when I have 2 accounts connected (one MSN and one JABBER) it tries to send my message to a jabber contact using the butterfly bus.

I'll try to patch this to get the real account.

Comment 3 Xavier Claessens 2006-11-11 09:54:52 UTC

Sorry it wasn't the problem !

The problem isn't really telepathy-specific. I'm using "xclaesse@gmail.com" for both MSN and jabber account and it breaks gossip because it stores accounts in hashtables using the ID as key... and guess what, if 2 accounts has the same ID it fails !

Comment 4 Martyn Russell 2006-11-11 18:24:51 UTC

This is probably slightly related to:
http://bugzilla.gnome.org/show_bug.cgi?id=322110

Also, can we use a proper title for this bug or mark it as a duplicate of the one mentioned above? Is this bug fixed by the bug #322110?

Comment 5 Xavier Claessens 2006-11-13 08:48:26 UTC

The patch doesn't apply anymore, I don't have time now to update it. But by reading the patch I'm not sure it will fix my problem. It says 2 contacts are different if the contact ID and his account ID are different, in my case the account ID are the same !

A solution is to use the account's unique_id instead of his id.

I think this bug is a dup of bug #322110 even if the patch proposed can't be used directly, the problem is the same.

Comment 6 Xavier Claessens 2006-11-13 21:50:29 UTC


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