#21 pidgin-otr: Incorrect XMPP resource displayed when doing multi-location messaging

[Ximin Luo]

Observed the following between A and B, who is logged in at B1 and B2

1. A "start a private conversation" with B
2. pidgin-otr says "Your buddy is logged in multiple times [etc]"
3. At this point, neither B1 nor B2 has said anything
4. In his OTR menu, A can indeed select between multiple sessions. However the entries both list the XMPP id for B (i.e. without the resource).
5. B1 says something to A.
6. Now both entries in A's menu list the XMPP id for B1 (including its resource). The entries actually represent B1 and B2's sessions, so A can still determine which one is B2 by manually asking questions in natural language (ugh :p)
7. B2 says something to A.
8. Now both entries show the correct XMPP id.

Sometimes the behaviour is different, e.g. step 4,5 are skipped, and initially both entries already show B1 (or B2)'s XMPP id, until the other speaks.

Also (this may be a separate bug), when receiving a message, there is no indication whether I received it from B1 or B2.

[Ian Goldberg]

On Sat, Jun 22, 2013 at 05:24:54PM +0000, Ximin Luo wrote:

---

** [bugs:#21] pidgin-otr: Incorrect XMPP resource displayed when doing multi-location messaging**

Status: open
Created: Sat Jun 22, 2013 05:24 PM UTC by Ximin Luo
Last Updated: Sat Jun 22, 2013 05:24 PM UTC
Owner: nobody

Observed the following between A and B, who is logged in at B1 and B2

1. A "start a private conversation" with B
2. pidgin-otr says "Your buddy is logged in multiple times [etc]"
3. At this point, neither B1 nor B2 has said anything
4. In his OTR menu, A can indeed select between multiple sessions. However the entries both list the XMPP id for B (i.e. without the resource).
5. B1 says something to A.
6. Now both entries in A's menu list the XMPP id for B1 (including its resource). The entries actually represent B1 and B2's sessions, so A can still determine which one is B2 by manually asking questions in natural language (ugh :p)
7. B2 says something to A.
8. Now both entries show the correct XMPP id.

Sometimes the behaviour is different, e.g. step 4,5 are skipped, and initially both entries already show B1 (or B2)'s XMPP id, until the other speaks.

Also (this may be a separate bug), when receiving a message, there is no indication whether I received it from B1 or B2.

Ximin,

Can you try the attached patch and see if it clears up the problem?

Thanks,

• Ian