I'm running MC5 with a Salut account configured. Running an example observer, an example handler and/or Empathy/mc5. I fire up a small Telepathy program that creates its own Salut Connection (from the same Connection Manager) and attempts to transfer a file to everyone else on the contact list. It finds the contact, but the channel never appears to the Observer or the Handler, or Empathy. Running tp-m-c with MC_DEBUG=1 produces no debugging output from when the FT channel is created. Empathy/mc4 correctly handles the incoming file and allows the user to accept it.
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.