TP-haze sometimes segfaults. I extracted this stack trace: telepathy-haze random SIGTRAP: #0 g_logv (log_domain=0x7f4ee1ef2806 "tp-glib", log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>, args=args@entry=0x7ffc4614b998) at gmessages.c:1046 #1 0x00007f4ee220ebe2 in g_log (log_domain=log_domain@entry=0x7f4ee1ef2806 "tp-glib", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=format@entry=0x7f4ee225615d "%s: assertion '%s' failed") at gmessages.c:1079 #2 0x00007f4ee220ec09 in g_return_if_fail_warning (log_domain=log_domain@entry=0x7f4ee1ef2806 "tp-glib", pretty_function=pretty_function@entry=0x7f4ee1efe4c0 <__func__.31694> "tp_base_connection_finish_shutdown", expression=<optimized out>) at gmessages.c:1088 #3 0x00007f4ee1df2e7c in tp_base_connection_finish_shutdown (self=<optimized out>) at base-connection.c:2905 #4 0x0000000000413eec in idle_finish_shutdown (data=0x872150) at connection.c:317 #5 0x00007f4ee2207b55 in g_main_dispatch (context=0x796350) at gmain.c:3122 #6 g_main_context_dispatch (context=context@entry=0x796350) at gmain.c:3737 #7 0x00007f4ee2207ec8 in g_main_context_iterate (context=0x796350, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #8 0x00007f4ee220818a in g_main_loop_run (loop=0x836650) at gmain.c:4002 #9 0x00007f4ee1ecb654 in tp_run_connection_manager (prog_name=prog_name@entry=0x422425 "haze", version=version@entry=0x4222f3 "0.8.0", construct_cm=construct_cm@entry=0x410150 <get_cm>, argc=argc@entry=1, argv=argv@entry=0x7ffc4614bcc8) at run.c:284 #10 0x000000000041001b in main (argc=1, argv=0x7ffc4614bcc8) at main.c:267
-- 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-haze/issues/67.
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.