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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jun 27 14:39:17 CEST 2011


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

--- Comment #8 from Simon Schampijer <simon at schampijer.de> 2011-06-27 05:39:17 PDT ---
(In reply to comment #5)
> > 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?

No, we do not get the ActivitiesChanged signal on A, which means that A can not
adjust the list of invitations accordingly, remove B from that list so that he
does not send him the uninvite signal anymore.

> 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.

I actually think there are two bugs: one is that A should not send an uninvite
signal if B did join already. The second bug is that B should handle an
uninvite signal cleanly and remove the previous invitation if it has not joined
yet (handled in #38712).

> 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.

I have attached the logs.

-- 
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.



More information about the telepathy-bugs mailing list