For gabble 0.16.4.1, initiating an empathy-call causes gabble to segfault. I get the following backtrace on launching empathy-call: Program received signal SIGTRAP, Trace/breakpoint trap. 0x00799cdf in g_logv (log_domain=0x65aa6f "GLib-GIO", log_level=G_LOG_LEVEL_CRITICAL, format=0x81c4b8 "%s: assertion `%s' failed", args1=0xbfffe7cc "\200\253e") at gmessages.c:758 758 G_BREAKPOINT (); (gdb) bt full #0 0x00799cdf in g_logv (log_domain=0x65aa6f "GLib-GIO", log_level=G_LOG_LEVEL_CRITICAL, format=0x81c4b8 "%s: assertion `%s' failed", args1=0xbfffe7cc "\200\253e") at gmessages.c:758 domain = 0x0 data = 0x0 depth = 1 log_func = 0x8068020 <log_handler> domain_fatal_mask = 5 masquerade_fatal = 0 test_level = 10 was_fatal = 0 was_recursion = 0 i = 3 #1 0x00799d85 in g_log (log_domain=0x65aa6f "GLib-GIO", log_level=G_LOG_LEVEL_CRITICAL, format=0x81c4b8 "%s: assertion `%s' failed") at gmessages.c:792 args = 0xbfffe7cc "\200\253e" #2 0x00799dc8 in g_return_if_fail_warning (log_domain=0x65aa6f "GLib-GIO", pretty_function=0x65ab80 "g_async_initable_real_init_finish", expression=0x65aaac "g_simple_async_result_is_valid (res, G_OBJECT (initable), g_async_initable_real_init_async)") at gmessages.c:801 No locals. #3 0x0055e7d1 in g_async_initable_real_init_finish (initable=0x83fe000, res=0x83dd070, error=0xbfffe880) at gasyncinitable.c:295 simple = 0xb76032f8 __PRETTY_FUNCTION__ = "g_async_initable_real_init_finish" #4 0x0055e611 in g_async_initable_init_finish (initable=0x83fe000, res=0x83dd070, error=0xbfffe880) at gasyncinitable.c:256 iface = 0x83cb038 __PRETTY_FUNCTION__ = "g_async_initable_init_finish" #5 0x08094e3e in call_channel_initialized (source=0x83fe000, res=0x83dd070, user_data=0x83b8b70) at media-factory.c:333 mcr = 0x83b8b70 priv = 0x81dd210 error = 0x0 #6 0x005ad3db in g_simple_async_result_complete (simple=0x83dd070) at gsimpleasyncresult.c:775 current_source = 0x81b3ad0 current_context = 0x818c4e8 __PRETTY_FUNCTION__ = "g_simple_async_result_complete" #7 0x005ad425 in complete_in_idle_cb (data=0x83dd070) at gsimpleasyncresult.c:787 simple = 0x83dd070 #8 0x00793651 in g_idle_dispatch (source=0x81b3ad0, callback=0x5ad3f1 <complete_in_idle_cb>, user_data=0x83dd070) at gmain.c:4781 No locals. #9 0x00790ffa in g_main_dispatch (context=0x818c4e8) at gmain.c:2691 dispatch = 0x793607 <g_idle_dispatch> ---Type <return> to continue, or q <return> to quit--- was_in_call = 0 user_data = 0x83dd070 callback = 0x5ad3f1 <complete_in_idle_cb> cb_funcs = 0x8864d0 cb_data = 0x81dd990 need_destroy = 1 current_source_link = {data = 0x81b3ad0, next = 0x0} source = 0x81b3ad0 current = 0x8195850 i = 1 __PRETTY_FUNCTION__ = "g_main_dispatch" #10 0x00791ab8 in g_main_context_dispatch (context=0x818c4e8) at gmain.c:3195 No locals. #11 0x00791ca3 in g_main_context_iterate (context=0x818c4e8, block=1, dispatch=1, self=0x8187880) at gmain.c:3266 max_priority = 0 timeout = 0 some_ready = 1 nfds = 4 allocated_nfds = 6 fds = 0x83bd978 #12 0x0079211d in g_main_loop_run (loop=0x8190648) at gmain.c:3460 self = 0x8187880 __PRETTY_FUNCTION__ = "g_main_loop_run" #13 0x002ac5b4 in tp_run_connection_manager (prog_name=0x8120abf "telepathy-gabble", version=0x8120ab6 "0.16.4.1", construct_cm=0x8067f28 <construct_cm>, argc=1, argv=0xbfffeb94) at run.c:285 connection = 0x8189ae8 bus_daemon = 0x818dc58 error = 0x0 ret = 1 __PRETTY_FUNCTION__ = "tp_run_connection_manager" #14 0x080682f6 in gabble_main (argc=1, argv=0xbfffeb94) at gabble.c:182 loader = 0x8187048 out = 134644064 fatal_mask = 13 #15 0x08067f24 in main (argc=1, argv=0xbfffeb94) at main.c:33 No locals.
Debug logs for gabble obtained from empathy-debugger follow: http://pastebin.com/k6FzK9qR
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/253.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.