Bug 25044

Summary: mission-control doesn't dispatch tube channels if prefered client does not handle text
Product: Telepathy Reporter: Youness Alaoui <youness.alaoui>
Component: mission-controlAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED INVALID QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: mission control log
dbus log

Description Youness Alaoui 2009-11-11 15:46:29 UTC 
I have a telepathy client that can only handle tube channels.
Requesting a dbus tube channel to the ChannelDispatcher makes it create a Text channel and gives it to Empathy for handling, it also creates a dbus tube channel, but it never calls my client's HandleChannels.
If I add Text channel to the handle filters, it works. The channel request is never dispatched, I never get a Succeeded or Failed signal on the ChannelRequest.
(I also notice that there's a deprecated Tubes channel that gets created, and that I cannot chat in the text channel from empathy, it shows in the 'Rooms' menu, but I have no way of accessing the window of the room).
Comment 1 Youness Alaoui 2009-11-11 15:46:59 UTC 
Created attachment 31120 [details]
mission control log
Comment 2 Youness Alaoui 2009-11-11 15:47:19 UTC 
Created attachment 31121 [details]
dbus log
Comment 3 Simon McVittie 2009-11-12 04:40:22 UTC 
Comment on attachment 31120 [details]
mission control log

>** (process:32226): DEBUG: telepathy-mission-control version 5.2.5

Please try with the latest MC release (5.3.2), which deals better with PreferredHandler, and probably also provides better logs.
Comment 4 Youness Alaoui 2009-11-12 12:26:07 UTC 
oh, sorry Simon, you're right, I apparently had an older version in /usr/local/ I removed it and started the 5.3.2 that I had installed previously, and it worked fine this time.
closing as invalid.

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.