Created attachment 24819 [details]
When I call RequestStream on a streamed media channel, I get always (9 times about 10) this error:
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/var/lib/python-support/python2.6/dbus/connection.py", line 214, in maybe_handle_message
File "test_mediachannel.py", line 117, in on_new_channel_user
File "test_mediachannel.py", line 186, in create_streams
DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** (test_mediachannel.py:7038): DEBUG: GetSessionHandlers returned 0 sessions
It's very surprising because yesterday my code worked correctly (without this error).
Finally, this is a problem with the server I used for my tests (jabber.fr) which is being slow to respond to disco.
So it isn't a telepathy problem.
I think this is a bug: RequestStreams taking ages isn't useful behaviour.
I wonder if closing a channel while RequestStreams is still waiting for caps would crash Gabble? :D
Forgot to reopen. And I can't move it to Reopened without a comment. I hate Bugzilla.
I don't think this is a libtelepathy bug, switching component :-P