[Bug 54061] something wrong in the dbus-tube offerer example

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=54061

--- Comment #1 from Will Thompson <will.thompson at collabora.co.uk> 2012-08-25 22:12:58 UTC ---
(In reply to comment #0)
> Can anyone run telepathy-glib/examples/client/dbus-tubes/.libs/offerer
> without noticing the following issues:
> 
> 
> At sometimes, the offerer fails to create the channel-
> 
> Breakpoint 1, channel_created (source=0x8060c18, result=0x805cc40,
> user_data=0x0) at offerer.c:155
> 155      GError *error = NULL;
> (gdb) n
> 159          TP_ACCOUNT_CHANNEL_REQUEST (source), result, NULL, &error);
> (gdb) 
> 158      channel = tp_account_channel_request_create_and_handle_channel_finish
> (
> (gdb) 
> 160      if (channel == NULL)
> (gdb) 
> 162          g_debug ("Failed to create channel: %s", error->message);
> (gdb) p error->
> code     domain   message  
> (gdb) p error->message 
> $5 = (gchar *) 0x805e3e8 "We are supposed to handle only one cDrive-by:hannel"
> 
> 
> This is happening since the CD is calling HandleChannels of the temporary
> handler with more than 1 channel bundle. At other times it works fine. Its a
> hit and miss.

This is bug 47760. I worked around it in LibreOffice by always requesting the
legacy Tubes channel for a contact before requesting the Tube channel, like
this: http://pastie.org/4588272 . It will be resolved when bug 32612 is
resolved.

> Next, everytime I escape the above, I get-
> 
> (process:18402): GLib-GObject-WARNING **: invalid cast from `TpChannel' to
> `TpDBusTubeChannel'
> 
> (process:18402): tp-glib-CRITICAL **: tp_dbus_tube_channel_offer_async:
> assertion `TP_IS_DBUS_TUBE_CHANNEL (self)' failed
> 
> 
> for the channel the offerer creates to begin with.

This sounds like the wrong channel factory is being used, so only a plain
TpChannel object is being created rather than a TpDBusTubeChannel subclass of
that object.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.