Summary: | no file transfer channels dispatched | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Danielle Madeley <danielle> |
Component: | mission-control | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Danielle Madeley
2009-08-10 18:01:36 UTC
You can see the channels waiting in the CM. Connection/salut/local_xmpp/Davyd_20Madeley/FileTransferChannel/0x... About 5 of them (I've run the example 5 times or so). FWIW, when you Disconnect a connection, it doesn't Close all of the channels, so those FT channels are still pending on the other end, even though the sending client has vanished. Is that expected behaviour? In the spec:
org.freedesktop.Telepathy.ChannelDispatcher
> Connections not created by the AccountManager are outside the scope
> of the channel dispatcher.
>
> Connections created by standalone Telepathy clients that do not
> intend to interact with the channel dispatcher should be ignored
> - otherwise, the channel dispatcher would try to launch handlers
> for channels that the standalone client was already handling
> internally.
So I think this is not a bug.
I don't think that part of the spec is relevant here. To clarify: I am opening a channel from a Connection not managed by the AM to a Connection managed from the AM that just both happen to be provided by the same CM. Logs, please. The MC debug log, the Salut debug log, version numbers of both, and possibly a dbus-monitor would all be useful. If you can construct a test case in MC's test/twisted framework that would be awesome, but if not, no big deal :-) Danni's old bug clearance bonanza. |
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.