Coccinella answers with wrong thread ID to chats created from a MUC room

Bug #394637 reported by Kevin "Zukero" POCHAT
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Coccinella
Invalid
Undecided
buzzdee

Bug Description

When using another client to connect to a MUC chat room where a Coccinella user is present, I try to create a private chat with this coccinella user. However, in coccinella, the replied are sent with a different thread ID than in the received message.
As a result, when the coccinella user sends a reply in this chat window, the other client thinks it is another chat, and opens another window/tab/whatever.
This has been seen on Coccinella 0.96.12 on Windows XP

Tags: muc
tags: added: muc
buzzdee (sebastia)
Changed in coccinella:
milestone: none → 0.96.20
Revision history for this message
buzzdee (sebastia) wrote :

I tried to reproduce this with pidgin, using a xmpp muc room, and was unable to reproduce the problem.

I entered the muc room with the pidgin client and as a different user with the coccinella client.

Starting a private chat with the coccinella client from the pidgin client opened a new window in the coccinella client, and the following conversation stayed in the same windows.

Starting the conversation from the coccinella client to the pidgin client did not open a new window, but when I later opened a private chat to the coccinella client from the pidgin client, then the messages from the coccinella client were all there already, I think this is more a problem with the pidgin client.

Trying the same between the two pidgin instances the things got even worse;)

What was the other client(s) that you tried to use?
Do you can verify with latest release of coccinella that the problem still exists?

In case there will be no answer before the next release, then we'll close the ticket.

Changed in coccinella:
assignee: nobody → buzzdee (sebastia)
Revision history for this message
buzzdee (sebastia) wrote :

I tried with tkabber, there everything works as expected.

Revision history for this message
buzzdee (sebastia) wrote :

Closing this one, since I got no feedback, and it seemed to work for me between coccinella clients, and between coccinella and tkabber. Blaming other clients ;)

Please reopen in case there is feedback regarding the other clients used.

Changed in coccinella:
status: New → Invalid
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.