Drops incoming messages after conversation timeout

Bug #532420 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-butterfly
Fix Released
Medium
telepathy-butterfly (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: telepathy-butterfly

If a conversation is left idle for a minute or two, the server will time it
out. If the remote end sends a message, a new conversation will be established.
papyon sees the reestablishment and subsequent messages, but any messages after
the reestablishment never get forwarded through to Empathy. If the conversation
is instead reestablished from the local end, messages can travel in both
directions without a problem.

To reproduce on one machine:
 1) Connect to one MSN account with Pidgin.
 2) Connect to another MSN account with Empathy.
 3) Start a conversation from Pidgin.
 4) Have a conversation.
 5) Say nothing for a minute or two until the switchboard disconnect.
 6) Send a message from Pidgin.
 7) Notice that Empathy has not seen the message.

I reported this upstream with a patch which I've been using for three weeks now. It was a week or so ago adapted and merged by upstream (http://bazaar.launchpad.net/~wgrant/telepathy-butterfly/master/revision/227). It would be great to have this patch in Lucid.

Related branches

Revision history for this message
In , Olivier Le Thanh Duong (olethanh) wrote :

Thanks a lot for the report and detailed analysis, I managed to reproduce the bug easily thanks to your instructions and extended your patch to make it more complete.

http://git.collabora.co.uk/?p=user/olethanh/telepathy-butterfly.git;a=shortlog;h=refs/heads/fix_attach_conversation

Revision history for this message
In , Jonny-lamb (jonny-lamb) wrote :

(In reply to comment #1)
> http://git.collabora.co.uk/?p=user/olethanh/telepathy-butterfly.git;a=shortlog;h=refs/heads/fix_attach_conversation

+ self._conversation= conversation
+ papyon.event.ConversationEventInterface.__init__(self, self._conversation)
+
+

Add a space before *and* after the equals sign, and remove the extra newline, and get mergin'.

Revision history for this message
In , Olivier Le Thanh Duong (olethanh) wrote :

Corrected and merged thanks

Revision history for this message
William Grant (wgrant) wrote :

Binary package hint: telepathy-butterfly

If a conversation is left idle for a minute or two, the server will time it
out. If the remote end sends a message, a new conversation will be established.
papyon sees the reestablishment and subsequent messages, but any messages after
the reestablishment never get forwarded through to Empathy. If the conversation
is instead reestablished from the local end, messages can travel in both
directions without a problem.

To reproduce on one machine:
 1) Connect to one MSN account with Pidgin.
 2) Connect to another MSN account with Empathy.
 3) Start a conversation from Pidgin.
 4) Have a conversation.
 5) Say nothing for a minute or two until the switchboard disconnect.
 6) Send a message from Pidgin.
 7) Notice that Empathy has not seen the message.

I reported this upstream with a patch which I've been using for three weeks now. It was a week or so ago adapted and merged by upstream (http://bazaar.launchpad.net/~wgrant/telepathy-butterfly/master/revision/227). It would be great to have this patch in Lucid.

Changed in telepathy-butterfly:
status: Unknown → Fix Released
Revision history for this message
Olivier Le Thanh Duong (olethanh) wrote :

FYI, I'm planning to make a telepathy-butterfly release tomorrow which contain this patch.
Regards,
Olivier

Revision history for this message
Olivier Le Thanh Duong (olethanh) wrote :

Thanks for the repoprt it's now Fixed in 0.5.6 which is packaged in lucid

Changed in telepathy-butterfly (Ubuntu):
status: New → Fix Released
Changed in telepathy-butterfly:
importance: Unknown → Medium
Changed in telepathy-butterfly:
importance: Medium → Unknown
Changed in telepathy-butterfly:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.