Version: 0.8.2 (using KDE 3.2.2, Gentoo) Compiler: gcc version 3.3.2 20040108 (Gentoo Linux 3.3.2-r6, propolice-3.3-7) OS: Linux (i686) release 2.4.26_pre6-gentoo If MSN disconnects in Kopete, it doesn't periodically try to reconnect. MSN just stays disconnected, until I return to the computer and see an obvious error message that MSN has disconnected and I manually reconnect MSN. And this is the behaviour with the Connection Status plugin *enabled*. Probably the reason the Connection Status plugin doesn't automatically try to reconnect MSN in this case is because my Internet connection never actually goes down - MSN just goes down on its own every so often (MSN just sucks that way - it's not Kopete's fault or anything). So instead of notifying the user of the obvious fact that MSN has been disconnected, forcing them to press OK to continue, Kopete should silently disconnect from MSN and silently try to reconnect to it periodically, until it succeeds. This is how gaim and other IM clients I've used work.
I have some more information on this behaviour (an easy way of reproducing it, for both MSN and ICQ): If I boot my laptop with my wireless card turned off and start Kopete, Kopete tries to connect to MSN and ICQ, and just keeps trying forever. As soon as I turn on my wireless card after I've started Kopete, nothing happens in Kopete - it doesn't succeed to connect to MSN or ICQ, even though the network is up, but just stays in the "connecting" state. If I try to manually disconnect and reconnect to ICQ or MSN, I can't - Kopete just keeps them in the "connecting" state and won't let me override it. Kopete is useless until I close and restart it. Again, this is the the "Connection Status" plugin enabled. (This plugin doesn't seem to be doing its job!) So basically the bug is this: If Kopete starts without an available network and the MSN and ICQ accounts are set to connect automatically, Kopete will never be able to connect to either of those protocols, even if the network comes up while Kopete is running. This is a pretty serious bug, especially with the growing popularity of WiFi.
*** This bug has been marked as a duplicate of 71077 ***