Bug 210734 - Please reintroduce active auto-reconnect functionality
Summary: Please reintroduce active auto-reconnect functionality
Status: REPORTED
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist with 20 votes (vote)
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-16 01:15 UTC by JR
Modified: 2009-12-13 16:58 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JR 2009-10-16 01:15:11 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

According to Google, there used to be a plugin that actively governed auto-reconnection of protocols. Please reintroduce it, as it covers several use-cases that the current passive dbus solution doesn't.

Reacting by reconnecting when the dbus call for "(interface) connection established" is sent /assumes/ that the server connection will never fail when the interface connection does not also fail.

Ergo, if the connection to the WLM server is lost due to bad wireless signal, yet not bad enough to completely disconnect the interface, Kopete won't reconnect. 

If you are connected to the Internet via a router, and the Internet connection to that router goes down, Kopete won't react as the (interface) network connection was never lost.

Likewise, if you are connected to an irc server and the server has to be restarted, Kopete won't react.
Comment 1 Christian Hartmann 2009-12-02 00:13:42 UTC
Yes that would be great! I also get disconnected sometimes and nearly always have to reconnect manually. I am using 0.80.2 with KDE SC 4.3.4 on openSUSE 11.2.
Comment 2 Joe Roberts 2009-12-02 05:19:27 UTC
Kopete constantly dumps connections on me for Yahoo and ICQ especially, but also on AIM - and does not reconnect afterward, or try to, as far as I can tell.  So maybe this plugin would help.  I'm not sure where to put this so I am putting it here.  If I should file a new bug, please let me know.

I am running kopete 0.80.2.  This is frustrating because it makes the application nearly useless - and it's a great app and does everything I need it to do, except in the case of maintaining / retrying connections.
Comment 3 JR 2009-12-13 16:58:50 UTC
(Semi-related; workaround.)

I pieced together a small bash script that sits in the background and checks every 5 minutes to see if any protocols are disconnected (via dbus commands).

As workarounds go it's been doing fine for a while now, so I cleaned it up a bit, commented it and uploaded it to sendspace. I wasn't sure what bugs.kde.org would think of me uploading (archived) arbitrary scripts to its attachment hosting.

http://www.sendspace.com/file/uc65wh

Since I had to start by learning rudimentary bash, it's 95% spaghetti and not really following any code conventions. There are probably bugs and unforeseen eventualities, too. Feel free to scour it for malware.

Note that one of the files in the archive is hidden (.reconnector.conf), and it will have to be placed in your home directory. You would also need to edit it and set up at least one protocol for the script to monitor.

The dbus interface to Kopete is nice but a bit limited, so don't expect too much of this. Some comments about this can be found in the .reconnector.conf file.