[Bug 31192] When the person that invited leaves a chat invitation is launched

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=31192

--- Comment #5 from Guillaume Desmottes <guillaume.desmottes at collabora.co.uk> 2011-06-27 04:26:14 PDT ---
(In reply to comment #4)
> When A quits the activity it tries to revoke the invitations and calls
> 'salut_olpc_activity_revoke_invitations' (
> http://cgit.freedesktop.org/telepathy/telepathy-salut/tree/src/salut-olpc-activity.c?h=telepathy-salut-0.4#n680
> ). As I understand it, this revokes the invitations that have been done to
> machines that have not accepted that invitation at this moment yet. For example
> A invites B and C, B did join, A quits and at that point the invitation to C
> should be revoked (side note: this actually is not handled cleanly see
> http://dev.laptop.org/ticket/11020). 

Yeah that's how it's supposed to work iirc.

> We seem to keep track of the invitations done and when it is accepted we try to
> remove the contact from our list (
> http://cgit.freedesktop.org/telepathy/telepathy-salut/tree/src/salut-self.c?h=telepathy-salut-0.4#n978
> ). The problem is that we do not get the SALUT_CONTACT_OLPC_ACTIVITIES changes
> on A (ActivitiesChanged), we only get signaled that the current activity of B
> changed. So we do not remove B from our list of invitations and hence when we
> quit the activity we try to revoke the invitation. I compared with a another
> sharing scenario without invitations where A shares publicly and B joins: here
> we do get the 'ActivitiesChanged' signal on A when B joins.

On which side (which salut) are you not getting the ActivitiesChanged signal?
B I guess?

So, if I understood things correctly I think the bug is in B which doesn't not
correctly handle the 'uninvite' stanza sent by A.

Would be good if you could post Salut logs from A and B. Try to generate them
with SALUT_DEBUG=all WOCKY_DEBUG=all GIBBER_DEBUG=all.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.