Version: 0.11.91 (using KDE 3.5.1, Gentoo) Compiler: gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8) OS: Linux (i686) release 2.6.14-gentoo-r2 Sometimes while chatting on MSN some messages fail to send. It takes a while, the Kopete logo in the toolbar spins for quite some time and then Kopete says that the message could not be sent. Strangely, on some days it works like a charm, but not all the time. Copying and pasting the message again works though. I tried gaim for some time and the error is not present there. Loaded plugins: History, Now Playing, MSN, ICQ Backtraces: n/a How to Reproduce: Not that easy... the bug occours infrequently and seemingly random 1. Open a chat with a MSN contact 2. Chat a bit. 3. Wait for a message saying that the message could not be sent for the connection is closed.
Update: I think it happens when the contact closes the message window while the message is being sent. I tested it with a second account. Steps to reproduce: 1. Open a chat with a second account on a second computer next to you. 2. Write some text to your second account 3. While the first account is sending, close the window of the second account. Here is the german (sorry) error message. A routh translation follows. [Nick]: hbhjbhjbhjbhbjhbhh [Nick] hat den Chat verlassen (Verbindung beendet). Die folgende Nachricht wurde nicht korrekt gesendet (Verbindung geschlossen): hbhjbhjbhjbhbjhbhh Translation: [Nick] has left the chat (Connection terminated). The following Message was not sent correctly (Connection terminated): ...
Ok, happens also without closing a window. Happened to me in a group chat now.
If your kopete is compiled with debug, please open your kopete with console, and send me the debug output when the disconnection happen. We need to know what is the commend that has been sent to the server which caused the disconnection Does your message contains suspicious word that may be eventually censored by Microsoft (i know they at least censor the word 'download.php' or '.src')
I compiled Kopete with debug support now, but I can no longer reproduce this bug. Somehow it just works now. I will try to give a better report when it turns up again.
Can't fix without more info