Bug 32519

Summary: names changed signal does not always fire on dbus muc tubes
Product: Telepathy Reporter: Marc Maurer <uwog>
Component: gabbleAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED NOTABUG QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: gabble log of the uwog20 side
gabble log of the uwog21 side

Description Marc Maurer 2010-12-20 02:09:30 UTC
Created attachment 41280 [details]
gabble log of the uwog20 side

Attached the log files for the following situation:

- uwog20 creates and offers a dbus muc tube to person uwog21
- uwog21 accepts the tube
- uwog20 closes the application (in this case AbiWord)

Bug: uwog21 does NOT get a 'names changed' signal

Observation: if uwog21 closes the application instead of uwog20, then the signal does get fired properly.
Comment 1 Marc Maurer 2010-12-20 02:09:57 UTC
Created attachment 41281 [details]
gabble log of the uwog21 side
Comment 2 Guillaume Desmottes 2010-12-20 02:37:47 UTC
Does Abiword closes the tube when exiting? It should (and close the Text channel as well).

Note that using TpAccountChannelRequest would prevent such issue as mission-control would close channels once their handlers have exited; but closing it manually is still a good idea.
Comment 3 Marc Maurer 2010-12-20 02:42:38 UTC
"Does Abiword closes the tube when exiting? It should (and close the Text
channel as well)."

At the moment not properly, no.

Why does it work properly when uwog21 exits btw? Because the tube was 'accepted' on that side by a TpBaseClient ?
Comment 4 Guillaume Desmottes 2010-12-20 02:43:56 UTC
Yeah exactly. When using TpBaseClient, mission-control knows that Abiword is handling the channels, so close them when needed.
Comment 5 Marc Maurer 2010-12-20 02:45:52 UTC
Excellent. Then I'll move the code over to TpAccountChannelRequest and close this as a non-issue.

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.