in long chat, using telepathy with yahoo sometimes will drop message, and sometimes the same message will show twice. the drop message problem is critical, i think it need to be fix soon. Reproducible: Sometimes
because it happened random, i do not know how to reproduced. is the telepathy did not has re-transmit function when the transmit is failed?
if you run ktp-debugger click on the tab marked "Haze" you should see debug information about what happens. It may contain some clue as to what is going wrong.
double message is occur and nothing special weird i just saw this first 2014年01月01日 00:40:37.876391 - [purple/yahoo] 166 bytes to read, rxlen is 186 2014年01月01日 00:40:37.876450 - [purple/yahoo] Yahoo Service: 0x06 Status: 1 second 2014年01月01日 00:40:41.519840 - [purple/yahoo] 1110 bytes to read, rxlen is 1024 2014年01月01日 00:40:41.519957 - [purple/yahoo] 1110 bytes to read, rxlen is 1130 2014年01月01日 00:40:41.520006 - [purple/yahoo] Yahoo Service: 0x06 Status: 1
i have saw the communition that the telepathy use to communication with yahoo is libpurple, which is the pidgin library.
i think maybe you need to see more the pidgin about using the yahoo account. in pidgin i did not receive that message drop problem. but since i using telepathy, it has been report that the message will drop. about the message drop, i need to tested more, because it is not always happened
mission control: 2014年01月01日 00:51:24.814471 - [mcd] mcd_connection_probation_ended_cb: probation finished, assuming connection is stable: /org/freedesktop/Telepathy/Connection/haze/yahoo/ Haze 2014年01月01日 00:53:29.206577 - [purple/yahoo] 6 bytes to read, rxlen is 26 2014年01月01日 00:53:29.206674 - [purple/yahoo] Yahoo Service: 0x0b Status: 1 2014年01月01日 00:54:26.194030 - [purple/yahoo] 259 bytes to read, rxlen is 279 2014年01月01日 00:54:26.194123 - [purple/yahoo] Yahoo Service: 0x06 Status: 1
2014年01月01日 00:49:24.285768 - [purple/yahoo] Unknown status key 213 2014年01月01日 00:49:24.285820 - [purple/yahoo] Unknown status key 300 2014年01月01日 00:49:24.285891 - [purple/yahoo] Unknown status key 440 2014年01月01日 00:49:24.285963 - [purple/yahoo] Unknown status key 301 2014年01月01日 00:49:24.286062 - [purple/yahoo] Unknown status key 550
i have reproduce maybe this problem. it problem between pidgin and telepathy communication. when it send a message that will split by message spilter in pidgin, the telepathy just receive some of the message. according to my test, when it send a large message, and it split to one large message and one blank message. telepathy just receive blank line.
demo video https://www.mediafire.com/folder/t3c4o58xdtpk0/
Created attachment 84389 [details] demo information
according to my friend, the above test is also drop message on pidgin. so i do not have the reproduce way for now
Created attachment 84491 [details] log i see it continued reconnect to yahoo.
i think it error is cause by first reconnect to yahoo and without talking anything. because it usually cause when there are times between talk.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!