Version: 0.6.2 (using KDE KDE 3.1.1) Installed from: Compiled From Sources Compiler: gcc (GCC) 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux When disconnecting from the internet and then conecting again with Kopete open, it is unable to reconnect and send any messages. This is with the ICQ-Plugin and with the IRC Plugin, too.
I have the same problem: I am using Kinternet to connect to a ISDN provider. Seems to me that it cannot handle a failed connect request and hangs them. There is no way to make it connect again. Only quit and restart...
The problem seems to be fixed in Kopete 0.7.1, at least for the MSN plugin. Everyone, please upgrade and test...
Subject: Re: [Kopete-devel] No reconnection after disconnect On Sunday 17 August 2003 22:17, Dik Takken wrote: > The problem seems to be fixed in Kopete 0.7.1, at least for the MSN > plugin. Everyone, please upgrade and test... It's not supposed to be fixed, so I think it's not worth the effort to try :)
Well, at least Kopete hasn't crashed when reconnecting to MSN since I compiled 0.7.1. Maybe you accidentally fixed something? Oh, don't worry, can happen to anyone.. :-)
Seems to be gone after upgrade to 0.7.1 and Suse 8.2
Seems to be fixed for ICQ, too. But NOT for IRC!
it is not fixed for me... kopete 0.7.1, kde 3.1.2, suse 8.0!! i have a lan with a dsl router, after the router looses the connection (disconnected from the provider) icq claims to be on "away" and is not able to reconnect, msn knows it is offline and has no problem to reconnect...
it's getting boring to hear the same crap over and over again, thanks.
it is not fixed for me... kopete 0.7.1, kde 3.1.3, suse 8.2!! After the isdn-connection was closed and opened again, kopete is not able to reconnect to the server via ICQ. Only a message "Connection with lost" appears. I have to quit kopete and start it again.
did you load the plugin called "connection status" ?
*** Bug 51583 has been marked as a duplicate of this bug. ***
use the connection status plugin if possible, that's what it's for
Using Kopete 0.7.2 *with* connection status plugin. It does not reconnect after the connection is lost (using Jabber)
> Using Kopete 0.7.2 *with* connection status plugin. It does not reconnect > after the connection is lost (using Jabber) The connection status plugin is only for temporary internent connections. Are you using dialup or PPPoE directly from the machine you're running Kopete on? Otherwise I think you misunderstand it's purpose.
No, I am not on a direct internet connection, I'm in a network. So, this bugreport does not apply to my situation? Should I submit another bugreport about my problem?
> So, this bugreport does not apply to my situation? That is correct. The connection status plugin monitors your netstat output, which never changes in a networked environment where your internet connection is "always on". > Should I submit another bugreport about my problem? What you're seeking is a way for the plugins to know when the socket has been disconnected unexpectedly, which I believe there are already open bug reports about (and unfortunately, no easy fix).
For me the problem is, that (no matter whether im on a direct connection or in some network) if the connection with the internet gets lost for whatever reason, the ICQ-Plugin does (a) not detect that the connection is lost and (b) does not allow any change in status from that point on... In particular im not able to set the status to "Offline" so that i can login again!! So the ICQ-Plugin is not available until restart of Kopete!! MSN-Plugin on the other hand reports correctly, that the connection to the service has been lost and switches to "Offline"... So the MSN-Plugin remains usable, all i have to do is select "Go online"!! I think that this behavior was the original motivation for the bug-report...
> MSN-Plugin on the other hand reports correctly, that the connection to the > service has been lost and switches to "Offline" I think this is probably because of the way the MSN protocol works. It sends periodic packets requiring acknowledgement to know that the connection is still open. AIM/ICQ have so such waste of bandwidth. But AFAIK it's not yes possible to tell when a socket has been disconnected, which is the solution for protocols like AIM/ICQ. > In particular im not able to set the status to "Offline" so that i can login > again!! So the ICQ-Plugin is not available until restart of Kopete!! Now that is a definite problem. One should always be able to manually force an account offline for reconnection. You may wish to file that as a separate bug. Maybe also this prevents connection status from disconnecting the ICQ account when a direct connection (like dialup) is destroyed?
If you read from a closed socket, the system will tell you it has closed. The socket classes when operating in buffering mode (i.e., doing the reading for you) also emit signals when the sockets close.
it does not work with kopete 0.9. my connection is established through network, so the network does not disconnect, it only disconnects on the server. but after the server reconnects, kopete does not. even if i wait for a day.
Hi, I also use a DSL-Router to connect to the internet. So I have/had the same problem. Since my router supports DynDNS I "abused" the connection status plugin to check if the IP has changed or not for my dyndns name. If someone is interested in the code please say so. (But beware. I am not the guru of programming. I just changed the code slightly to fit my needs. Furthermore am I not able to fully understand how all things in kopete work together. So don't expect too much. --> It works for me but not nessesarily for you.)
I (and I can't help feeling most people) are suffering the same problem that Dominik reported (and with 0.9). There basically is no auto-reconnect (with MSN at least) for Kopete, making Gaim waaaaay better for every day use.
it's the same for version 0.12.4 and yahoo protocol- so pls reopen