Bug 14368 - Messages coming from 'ghost' participants
Summary: Messages coming from 'ghost' participants
Status: NEW
Alias: None
Product: Telepathy
Classification: Unclassified
Component: pymsn (show other bugs)
Version: unspecified
Hardware: x86 (IA32) All
: medium normal
Assignee: Ali Sabil
QA Contact: Telepathy bugs list
Depends on:
Reported: 2008-02-04 06:26 UTC by Stéphan Kochen
Modified: 2008-02-04 06:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Testcase showing messages from 'ghost' participants. (3.03 KB, text/x-python)
2008-02-04 06:26 UTC, Stéphan Kochen

Description Stéphan Kochen 2008-02-04 06:26:30 UTC
Created attachment 14137 [details]
Testcase showing messages from 'ghost' participants.

In some cases, an object implementing the ConversationEventInterface can lose track of participants, because no notifications are sent. For example:

- Someone opens a chat with the PyMSN application.
- The PyMSN client gets a call to on_invite_conversation, the client knows about initial participants.
- The PyMSN client gets a message from the other participant.
- The other participant leaves the conversation, and PyMSN registers this by calling on_conversation_user_left.
- The same person opens a chat again, no notification of this is received by the PyMSN client.
- The PyMSN client gets a message from this 'ghost' participant (on the same ConversationEventInterface object as before).

A testcase for the above situation is attached.

Possibly related:
Alongside this, my PyMSN application actively starts conversations with buddies. It creates a new Conversation and ConversationEventInterface object only if it cannot find an existing conversation for a particular buddy.

After a while it loses track, and simply recreates these objects. The problem here is that every message starts arriving on all ConversationEventInterface objects.

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.