| Summary: | Invalid g_source_remove use leads to error with new glib (2.39) | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Sebastien Bacher <seb128> |
| Component: | tp-glib | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Sebastien Bacher
2013-12-04 10:56:53 UTC
Confirming, since that glib update Jabber (through t-gabble) cannot connect due to this crash. Seems like it could be rather a bug in telepathy-glib, other connectors have the same issue, e.g telepathy-salut
"#0 0xb72e015d in g_logv (log_domain=log_domain@entry=0xb732040e "GLib",
log_level=<optimized out>, log_level@entry=G_LOG_LEVEL_CRITICAL,
format=format@entry=0xb7326dcc "Source ID %u was not found when attempting to remove it", args=args@entry=0xbfb5dddc "\005")
at /build/buildd/glib2.0-2.39.1/./glib/gmessages.c:1019
#1 0xb72e0273 in g_log (log_domain=log_domain@entry=0xb732040e "GLib",
log_level=log_level@entry=G_LOG_LEVEL_CRITICAL,
format=format@entry=0xb7326dcc "Source ID %u was not found when attempting to remove it") at /build/buildd/glib2.0-2.39.1/./glib/gmessages.c:1059
#2 0xb72d7a5c in g_source_remove (tag=5)
at /build/buildd/glib2.0-2.39.1/./glib/gmain.c:2210
#3 0xb71af8ab in no_more_connections (conn=0x9d419e8) at run.c:113
#4 0xb73a7549 in g_cclosure_marshal_VOID__VOIDv (closure=0x9d4c888,
return_value=0x0, instance=0x9d419e8, args=0xbfb5dfac "",
marshal_data=0x0, n_params=0, param_types=0x0)
at /build/buildd/glib2.0-2.39.1/./gobject/gmarshal.c:115
#5 0xb73a5aee in _g_closure_invoke_va (closure=closure@entry=0x9d4c888,
return_value=return_value@entry=0x0, instance=instance@entry=0x9d419e8,
args=args@entry=0xbfb5dfac "", n_params=0, param_types=0x0)
at /build/buildd/glib2.0-2.39.1/./gobject/gclosure.c:840
#6 0xb73bee70 in g_signal_emit_valist (instance=instance@entry=0x9d419e8,
signal_id=signal_id@entry=7, detail=detail@entry=0,
var_args=var_args@entry=0xbfb5dfac "")
at /build/buildd/glib2.0-2.39.1/./gobject/gsignal.c:3238
#7 0xb73bf9e3 in g_signal_emit (instance=instance@entry=0x9d419e8,
signal_id=7, detail=detail@entry=0)
at /build/buildd/glib2.0-2.39.1/./gobject/gsignal.c:3386
#8 0xb70c5def in connection_shutdown_finished_cb (conn=0x9d54108,
data=0x9d419e8) at base-connection-manager.c:642
#9 0xb73a7549 in g_cclosure_marshal_VOID__VOIDv (closure=0x9d4f450,
return_value=0x0, instance=0x9d54108, args=0xbfb5e17c "\r",
marshal_data=0x0, n_params=0, param_types=0x0)
at /build/buildd/glib2.0-2.39.1/./gobject/gmarshal.c:115
#10 0xb73a5aee in _g_closure_invoke_va (closure=closure@entry=0x9d4f450,
return_value=return_value@entry=0x0, instance=instance@entry=0x9d54108,
args=args@entry=0xbfb5e17c "\r", n_params=0, param_types=0x0)
at /build/buildd/glib2.0-2.39.1/./gobject/gclosure.c:840
#11 0xb73bee70 in g_signal_emit_valist (instance=instance@entry=0x9d54108,
signal_id=signal_id@entry=21, detail=detail@entry=0,
var_args=var_args@entry=0xbfb5e17c "\r")
at /build/buildd/glib2.0-2.39.1/./gobject/gsignal.c:3238
#12 0xb73bf9e3 in g_signal_emit (instance=instance@entry=0x9d54108,
signal_id=21, detail=detail@entry=0)
at /build/buildd/glib2.0-2.39.1/./gobject/gsignal.c:3386
#13 0xb70c3c27 in tp_base_connection_finish_shutdown (self=0x9d54108)
at base-connection.c:2896
#14 0x0807f310 in ?? ()
#15 0xb7455515 in g_simple_async_result_complete (simple=0x9d37618)
at /build/buildd/glib2.0-2.39.1/./gio/gsimpleasyncresult.c:777
#16 0xb769e640 in ?? ()
from /usr/lib/telepathy/salut-0/lib/libwocky-telepathy-salut-0.8.1.so
..."
Already fixed in git for 0.20.5 (if ever released), 0.22.1 and 0.23.1. Sorry, no release yet (I think all the maintainers are doing other things). http://cgit.freedesktop.org/telepathy/telepathy-glib/commit/?id=3c1c43cc2a13df3d5f56e20d49c7bd136486b372 Thanks Simon, the fix is indeed working! |
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.