When ensuring a channel of type org.freedesktop.Telepathy.Channel.Type.StreamTube for use with rfb, Mission Control 5 despatches two channels, one of that type, and a (I beleive, compatability one of type) org.freedesktop.Telepathy.Channel.Type.Tubes. I'm not interested in the x.Type.Tubes channel, but it seems that it is necessary for this to be handled in order for the x.Type.StreamTube one to work. However, because the x.Type.Tubes one always has Requested=false on it, even when it was requested locally, it is impossible for me to correctly start the correct rfb client or server depending on whether the channel was requested locally or not (since this breaks client handler filters).
[11:46:10] <grundleborg> smcv: is it gabble's fault or MC's fault that when a StreamTube channel is despatched with Requested=true, the corresponding Tubes channel despatched for compatability has Requested=false? [11:46:21] <smcv> grundleborg: spec. you didn't ask for it [11:46:33] <grundleborg> oh joy [11:46:37] <smcv> grundleborg: I should patch MC to add Tubes to its ContactList special case [11:46:48] <smcv> grundleborg: (channels that it won't close even if it can't find a handler for them) [11:46:57] <grundleborg> yeah, that would be great [11:47:09] <smcv> grundleborg: and tbh during Gabble 0.9 we should just delete the old Tubes channels [11:47:12] <grundleborg> because at the moment, this breaks starting the tube server or client application correctly [11:47:15] <grundleborg> yes!!!!!!! [11:47:23] <grundleborg> that would be great!!! [11:47:25] <smcv> grundleborg: file a bug on MC please, or I'll forget
Fixed in 5.2.2
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.