I don't get this. The line where an assertion is clearly not satisfied
is wocky-c2s-porter.c:1377. Yet, in gabble 0.13.5 this is the line:
1374 if (!wocky_xmpp_connection_send_close_finish (WOCKY_XMPP_CONNECTION
(source),
1375 res, &error))
1376 {
1377 g_simple_async_result_set_from_error (priv->close_result, error);
1378 g_error_free (error);
1379
1380 goto out;
1381 }
So g_simple_async_result_set_from_error, but that's a real symbol (not
inline or a macro) and we don't get a frame for
g_simple_async_result_set_from_error in the backtrace so it seems to be
failing in close_sent_cb?
However, there's no typecheck there? so I don't understand what's
actually failing here. If we could see what assertion is actually being
logged failing that would be useful. Perhaps look in xsession-errors?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/867682
Title:
telepathy-gabble crashed with signal 5 in
g_simple_async_result_complete()
To manage notifications about this bug go to:
https://bugs.launchpad.net/telepathy-gabble/+bug/867682/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
