| Summary: | messages lost in a certain scenario | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Nicolò Chieffo <84yelo3> |
| Component: | butterfly | Assignee: | Telepathy bugs list <telepathy-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | major | ||
| Priority: | high | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | butterfly.log | ||
|
Description
Nicolò Chieffo
2009-06-16 14:40:52 UTC
do you mean if he come back online again and he send you a message you won't see it? Yes It's like it uses the same channel as the one used when the chat started? Is it possible that it's empaty's fault? Do you need a log? Created attachment 27185 [details] butterfly.log Here's the comments: 1) I connected with yelo_3@yahoo.it in empathy 2) I connected with chieffo.nicolo@studio.unibo.it in pidgin 3) I opened a chat from empathy to pidgin saying "HELLO" (in the log at line 61) 4) I disconnected in pidgin 5) I sent another message from empathy to pidgin "THIS MESSAGE IS SENT WHEN THE USER IS OFFLINE" (line 92) 6) I reconnected in pidgin 7) I sent a message from pidgin to empathy "THIS MESSAGE IS NOT RECEIVED" (line 112) 8) I closed the pidgin chat window to yelo_3@yahoo.it and reopened it 9) I sent another message from pidgin "ALSO THIS MESSAGE IS NOT RECEIVED (AFTER CLOSING AND REOPENING THE OTHER SENDER'S WINDOW)" (line 153) 10) I closed the empahty chat window to chieffo.nicolo@studio.unibo.it 11) I sent another message from pidgin "NOW THAT I HAVE CLOSED EMPATHY CONTACT WINDOW THIS MESSAGE SHOULD BE RECEIVED" (line 225) unfortunately also that message isn't received, so I was wrong at the beginning, no other message can be delivered until I disconnect and reconnect from empathy (or maybe I have to try to send something from empathy to pidgin to see what happens?) I've also checked with tp-haze, which works correctly Looks like a serious bug indeed. yes, it should really be a blocker for the next release Hello, this bug is still there in 0.5.1 It really needs some attention by some developer According to Nicolò the offline branch fix this, the branch have merged into mastee |
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.