I have two different Jabber accounts configured in empathy. I can use one or the other one, everything works. But telepathy-gabble crashes when I try to connect both. I have this line in dmesg each time (numbers change): traps: telepathy-gabbl[20658] trap int3 ip:7fdc68120c0e sp:7fff90288770 error:0 I have tried to re-create the accounts, remove everything I can in ~/.local/share/evolution/addressbook/system and ~/.local/share/telepathy/mission-control/, nothing changes. Everything was working well until now, I could be connected to both without a problem before. I have tried 0.16.7 and 0.18.1 (just changed the version of the ebuild), no difference. The bug appears very early, as soon as I try to connect the second account. It even crashes if the second account is a "fake" account (a random address used as contact identifier).
Please get a proper backtrace: https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces Once packages are compiled properly, you can install abrt and start it to let it catch the failures
I'm not sure that I've got what you want, but here's what I have in gdb: (telepathy-gabble:16955): GLib-CRITICAL **: Source ID 4 was not found when attempting to remove it [New Thread 0x7fffed9ec700 (LWP 16965)] [Thread 0x7fffed9ec700 (LWP 16965) exited] Program received signal SIGTRAP, Trace/breakpoint trap. 0x00007ffff63c7c0e in g_logv () from /usr/lib64/libglib-2.0.so.0 (gdb) bt #0 0x00007ffff63c7c0e in g_logv () from /usr/lib64/libglib-2.0.so.0 #1 0x00007ffff63c7d82 in g_log () from /usr/lib64/libglib-2.0.so.0 #2 0x00007ffff63bf99c in g_source_remove () from /usr/lib64/libglib-2.0.so.0 #3 0x00007ffff3e0eeec in ffi_call_unix64 () from /usr/lib64/libffi.so.6 #4 0x00007ffff3e0e8f2 in ffi_call () from /usr/lib64/libffi.so.6 #5 0x00007ffff68b5b10 in g_cclosure_marshal_generic () from /usr/lib64/libgobject-2.0.so.0 #6 0x00007ffff68b51f7 in g_closure_invoke () from /usr/lib64/libgobject-2.0.so.0 #7 0x00007ffff68c7947 in ?? () from /usr/lib64/libgobject-2.0.so.0 #8 0x00007ffff68cf86c in g_signal_emit_valist () from /usr/lib64/libgobject-2.0.so.0 #9 0x00007ffff68cfa82 in g_signal_emit () from /usr/lib64/libgobject-2.0.so.0 #10 0x00007ffff712421e in ?? () from /usr/lib64/libtelepathy-glib.so.0 #11 0x00007ffff3e0eeec in ffi_call_unix64 () from /usr/lib64/libffi.so.6 #12 0x00007ffff3e0e8f2 in ffi_call () from /usr/lib64/libffi.so.6 #13 0x00007ffff68b5b10 in g_cclosure_marshal_generic () from /usr/lib64/libgobject-2.0.so.0 #14 0x00007ffff79b6ebf in ?? () from /usr/lib64/libdbus-glib-1.so.2 #15 0x00007ffff7785265 in ?? () from /usr/lib64/libdbus-1.so.3 #16 0x00007ffff777a911 in dbus_connection_dispatch () from /usr/lib64/libdbus-1.so.3 #17 0x00007ffff79b41d5 in ?? () from /usr/lib64/libdbus-glib-1.so.2 #18 0x00007ffff63c0aab in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #19 0x00007ffff63c0ce4 in ?? () from /usr/lib64/libglib-2.0.so.0 #20 0x00007ffff63c112a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #21 0x00007ffff7205db3 in tp_run_connection_manager () from /usr/lib64/libtelepathy-glib.so.0 #22 0x000000000042a56c in gabble_main (argc=1, argv=0x7fffffffdf38) at gabble.c:177 #23 0x00007ffff5dcfb4d in __libc_start_main () from /lib64/libc.so.6 #24 0x000000000042a18d in _start () Then, typing "continue" in gdb make telepathy-gabble work perfectly with both accounts connected (!). I can compile other packages with -ggdb or other flags if you want. I've never used abrt before, but I can spend some time finding how it works if you prefer.
The bug has been reported and fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=72303
Are you using that newer glib version?
Yes, and it's not in the main portage repository. Sorry for the noise, I should have checked that before, you can safely close the bug.
OK, thanks for feedback :)
