Version: 0.12.3 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux Trying to connect to the MSN network, I get a similar outcome as bug 68204, ie: the icon for the connection flaps its wings a few times, then turns grey. However, this is not a duplicate, for two reasons, number one, the previous bug is classed as resolved, number two, I get this on running from Konsole: kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 10! kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 10! kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection) kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 0! kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 0! kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection) kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 0! kopete (msn): WARNING: [QString MSNNotifySocket::statusToString(const Kopete::OnlineStatus&) const] Unknown status 0! kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection) kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection) This problem has prevented me from connecting despite numerous restarts of the client. I had similar problems before, which I could get around by setting my sign-in status to "Away" or "Busy", but these seemed to have stopped working.
*** Bug 137445 has been marked as a duplicate of this bug. ***
Its seemed to perk up a bit, but still requires the signing in as away every now and then. Just to confirm, I'm not running a proxy, or running through a proxy. Joe
Well, my MSN connection problem described in Bug 137445 started in March 2006, but I had that problem only with the socks proxy. Without a proxy it worked well. The problem continuously exists since March, I was just too lazy to file a bug. Now it seems that I am having this problem even when not behind a proxy, but I am not sure whether my problem is the same as this bug as as I _can_ connect sometimes. Does this problem always prevent you connecting?
*** Bug 142354 has been marked as a duplicate of this bug. ***
I'm having pretty much the same problems. Sometimes I cant connect to MSN at all, other times. And it allways disconnect here and then, VERY annoying. I'm using kopete 3.5.5-r2 on gentoo, compiled with gcc-4.1.1.
*** Bug 140442 has been marked as a duplicate of this bug. ***
Same problem here. Can connect but get disconnected after few seconds. I am using Kopete 0.12.5 with KDE 3.5.7 on Gentoo I get error messages on the konsole: kopete (msn): WARNING: [void MSNSocket::slotSocketError(int)] Error: 17 (remote host closed connection) Very strange! got a DCOPReply opcode, but we were not waiting for a reply!
*** This bug has been confirmed by popular vote. ***
Connecting to MSN is working fine here (Kopete 0.12.5, KDE 3.5.7).
Sometimes the MSN servers are flaky. This was probably one of those times. Reopen if you have a persistent problem connecting to MSN with 0.12.6.
I have problems with 0.12.7... My output: Very strange! got a DCOPReply opcode, but we were not waiting for a reply And a LOT of QGArray::at: Absolute index -n out of range. 0<n>more of 1000 :S Im only in wireless, is strange.
THIS BUG IS NOT SOLVED