[farsight2/master] Dont use g_timeout_add_seconds, its really broken (gnome bug #448943)
Olivier Crête
olivier.crete at collabora.co.uk
Tue Dec 23 15:21:24 PST 2008
---
transmitters/rawudp/fs-rawudp-stream-transmitter.c | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/transmitters/rawudp/fs-rawudp-stream-transmitter.c b/transmitters/rawudp/fs-rawudp-stream-transmitter.c
index a173bab..8df1eeb 100644
--- a/transmitters/rawudp/fs-rawudp-stream-transmitter.c
+++ b/transmitters/rawudp/fs-rawudp-stream-transmitter.c
@@ -1070,10 +1070,9 @@ fs_rawudp_stream_transmitter_start_stun (FsRawUdpStreamTransmitter *self,
data->component_id = component_id;
g_mutex_lock (data->self->priv->sources_mutex);
-#if GLIB_CHECK_VERSION (2, 14, 0)
- /* This is MAY broken in GLib 2.14 (gnome bug #448943) */
- /* If the test does not stop (and times out), this may be the cause
- * and in this case should be investigated further
+#if 0
+ /* This IS broken in GLib 2.14.6
+ * See http://bugzilla.gnome.org/show_bug.cgi?id=448943
*/
self->priv->stun_timeout_id[component_id] = g_timeout_add_seconds_full (
G_PRIORITY_DEFAULT, self->priv->stun_timeout,
--
1.5.6.5
More information about the farsight-commits
mailing list