GNOME Bugzilla – Bug 661158
Empathy crash in _tp_contacts_from_values
Last modified: 2011-10-12 14:10:29 UTC
I get this crash 1 or 2 minutes after I connect to my account. I use only one Jabber account. I use telepathy-glib 0.15.7 Trace :
+ Trace 228703
Thread 1 (Thread 0x7f496f034900 (LWP 21699))
I also get in .xsession-errors file : tp-glib:ERROR:util.c:1961:_tp_contacts_from_values: assertion failed: (G_IS_OBJECT (value)) (gnome-shell:1404): telepathy-WARNING **: tpf-persona-store.vala:617: Lost connection to the telepathy-logger service. (gnome-shell:1404): telepathy-WARNING **: tpf-persona-store.vala:617: Lost connection to the telepathy-logger service. The crash seems to only happen when I join a Jabber MUC. I use : - empathy 3.2.0.1 - telepathy-farsight 0.0.19 - telepathy-farstream 0.1.1 - telepathy-gabble 0.12.7 - telepathy-glib 0.15.7 - telepathy-logger 0.2.10 - telepathy-mission-control 5.9.3 - telepathy-qt4 0.7.3
Thanks for the bug report. That's a telepathy-glib crash so I forwarded it to https://bugs.freedesktop.org/show_bug.cgi?id=41697
I didn't manage to reproduce this bug. Does it always happen when joining a specific muc?
(In reply to comment #3) > I didn't manage to reproduce this bug. Does it always happen when joining a > specific muc? Nevermind, I fixed it in tp-glib.
I have installed tp-glib from master this morning and I haven't get the crash. Thank you very much. I wonder if it would be possible to make Empathy more robust to this kind of Telepathy crash. Instead of crashing, maybe catch the abort signal in the Telepathy code (or something like that, I'm not a C developer) then display a message to the user like « Something was wrong in a Telepathy component... ».
Empathy won't crash if another Telepathy component (CM) crashes. But in this case the bug was in tp-glib on which Empathy is linking so the crash was happening in the Empathy process; not much we can do in this case.
OK, thank you for the information.