Version: 0.8.90 (CVS >= 20040123) (using KDE 3.2.90 (CVS >= 20040117), compiled sources) Compiler: gcc version 3.3.1 (Mandrake Linux 9.2 3.3.1-4mdk) OS: Linux (i686) release 2.6.3 My kopete doesn't reconnect after a disconnection from internet or from the server, even if I enabled Connection Status plugin.
I'll be working on this later in the months ahead.
Is there anything to report on this? Sorry to be impatient! Sadly my connection gets terminated so frequently that I got fed up of reconnecting and am now using gaim.
Hi, on http://www.rangun.de/projects.html you can find a patch to kopete, which could help you. Just switch to the netstat method in the configuration dialog. Use this plugin instead of the connection status plugin. Metta Heiko
The solution in Comment 3 uses smpppd which, as far as I can understand, means it only works with dialup/pppoe connections. In my case I have a router managing the ADSL connection, and this won't work. I propose a more generic solution (perhaps part of the connection status plugin): If the user is disconnected due to a dropped network connection (and the net connection still appears to be active), try to reconnect every x minutes. Tell the user about the connection attempts using a popup bubble which would contain a "stop trying" button.
The plugin in Comment 3 uses both netstat and smpppd. It replaces the connection status plugin (netstat only) and adds some more reliability.
There is some support for auto-reconnect in CVS. There's no popup bubble with a "stop trying button"; instead you need to notice it's reconnecting, and stop it with the account's context menu.
Created attachment 8352 [details] replacement for the connectionstatusplugin.cpp go to the line where the dns-name must be entered and replace it with your dns
Created attachment 8353 [details] this is the corresponding connectionstatusplugin.h there is a small change in this file to make the changes work
I had the same problem with my dsl-router-connection. What I came up with was not to monitor the netstat but the IP-address of the dns of the DynDNS.org accout that is running on the router. When that changes it reconnects. This works for my setup. But I don't know how usefull it is for yours. (You need a DynDNS.org account and probably access to the router as well.)
Created attachment 8354 [details] smpppdcs-Plugin for KDE 3.3.1 For me it works with the plugin mentioned in Comment #3. It is an enhancement to the connection status plugin. Don't be irritated by the name smpppdcs, it uses netstat too and will be renamed if it will get integrated into the kopete cvs. I've attached a patch (for KDE 3.3.1).
*** Bug 95328 has been marked as a duplicate of this bug. ***
*** Bug 97352 has been marked as a duplicate of this bug. ***
We really do need a way of reconnecting if the network interface DOESN'T go down. For me, kopete runs through eth0, which is always up. The DSL may not always be, and the server might disconnect me for a variety of reasons. However, if the connection is lost, kopete should wait for a configurable time and then try to reconnect a configurable number of times.
I'm in comment #2 - I returned to Kopete because of its better KDE integration, but after a week I'm already bored of manually reconnecting! I can't just press the "Connect All" button because one of my accounts is used for a separate job and I'm only online with that when working my scheduled hours on it - instead, I have to reconnect the various accounts manually. Gaim doesn't get it perfectly right though - every time it reconnects to an account, it pops up the "Buddies" list on screen again, and you have to minimise it each time. It also pops up a passive window which you can't turn off telling you its reconnecting. It should just do it quietly and only tell you if there's a permanent failure, or if it fails on a second attempt, and that should be configurable.
IMO it should not try to reconnect if it is disconnected because of a connection to the same account on another computer. I have seen this behavior in gaim.
Why not simply use the same method as knemo on kde-apps.org to monitor if an interface is up or not? knemo allows you to select the interface which will be used for the internet connection.. in my case that's ppp0. As for automatic reconnection, simply keep monitoring the interface till its up again and then reconnect! knemo works very well for me... I would love it if kopete were to have similar functionality. And I just tried the connection status plugin again and disconnected my adsl connection while i was signed in on MSN. It didn't seem to notice that the internet connection had gone down!
There is a problem with monitoring the network interface - your internet connection can go down without your interface going down if you are on a LAN. This would apply to anybody using NAT, or anybody on an ordinary network. About the only people that this solution would actually work for are those using PPP(/oE). Lots of things can cause the connection to go down besides having the interface go down. Wouldn't it make more sense just to notice when the connection is dropped. The software already sends a notification when it happens, so the event trigger is already there to tap into...
I'd highly recommend a look into how HAL, hotplug, etc. can help with the situation. Hooks into what NetworkManager does via DBUS<->HAL should definitely be explored.
just my 0.02¢: My interface is eth0. Always. I'm behind a NAT-Router. My connection is dropped every 24hrs. Monitoring interfaces wouldn't help. Monitoring interfaces is crap at all. You're connected to a server and as soon you get the disconnecting info (timeout, no answer, some kind of message, whatever, you name it), you should reconnect in a quietly manner. Perhaps you have to send pings or similar to find out that you're disconnected. Perhaps you can query status-infos every few minutes from the server. Whatever, there're plenty of things to query and monitor to find out that the connection is lost. Every time you send or query data to/from the server you should notice a dropped connection. For idle times (no send/query command from the user) you could do some kind of background monitoring (get status info from server every few minutes). All in all, it should be *seamless* and configurable. No dialogs please, bubbles are more than enough.
i have kde 3.5.1 and reconnect for example with yahoo still doesn't work
kde 3.5.2, jabber doesn't automaticaly reconnect and issue a popup :'( Why not simply add a configuration instruction in the status plugin ? It should be simple to add a general configuration (for all protocol), no ? and an overide config for desired protocol (for example msn that don't support multiple connection with same account so allow to not reconnect if there is a connection from somewhere else). (for jabber, add a random string on the ressource if disconnected because of a connection from somewhere else). It would be a realy proper way of handle that... Base the reconnection on the pppoe/dyndns/remote server that show the public ip is a dirty hack, because it will makes the kopete reconnection not automatic. Gaim is not the better way but it has the reconnect (everytime everwhere not intelligent) option, it's anoying for the status reconnection box (which is hideable with a special window config : reduce/no focus/ignore from window manadger/etc). There is a lot of complain of this bug, I will help how much I could by testing everything and report bugs. So please dear developper, I love your works, choose the better/intelligent/worldworking way, makes the code and we will test ;) Even a stupid plugin would be ok, but we need to not follow the windows fucking way : nothing works, popup everywhere, manual reconnection, etc... (we love our kde, not win(2000->xp->shit), so stop follow their design ;) )
Definitely the solution that involves ppp stuff or network interface card status monitoring is not the best, as it assumes that the disconnection is caused by some error in the local hardware. As some have suggested, what should be done is to handle the connection closed socket event, and after that retry in a couple of secs. intervals. If the connection is restored in a short time (say <1 min), only a yellow balloon saying something like "Disconnected but reconnected to service", and if it takes longer to reconnect, two balloons could be showed, first one saying "Lost connection to service" and another one, when the connection is restored, saying "Connection to service successfully restored".
i have a dsl-modem-router i'm connected to, if i request teh connection via my eth, dsl-modem gets connected and allows me to contact internet. Here's what happens on my comp. I boot into KDE - kopete starts automatically - gadu connects and yahoo icon just keeps jumping and never stops. I have to manualy set yahoo status to "unavailable" and then to "online" and now ym connects without a problem instantly
this feature will be important for wifi user because the auto connect try to connect before the wifi is up => don't work :-( thanks in advance
I concur, this is highly annoying especially when on a wifi...
The message you sent requires that you verify that you are a real live human being and not a spam source. To complete this verification, simply reply to this message and leave the subject line intact. The headers of the message sent from your address are show below:
Implemented for KDE4 using Solid, backported via patches to openSUSE 10.3 and (I think) Pardus Linux.