Version: 1.3.1 (using KDE 4.6.2) OS: Linux If the WiFi connection is interrupted, Konversation does not reliably reconnect to the irc server when the network is back. Even a manual reconnection to the irc server does not succeed all the time. It takes usually on or more retries until the connection is established. If the retry does not succeed, the log mentions that there would be no network connection, although there actually is. Note that Wicd is my network manager and Konversation uses default settings. Reproducible: Always OS: Linux (i686) release 2.6.38-ARCH Compiler: gcc
Could you please quote the log entries you mention?
[18:59] [Mode] You have set personal modes: +i [19:03] [Info] Disconnected from chat.freenode.net (port 8001). [19:03] [Info] Network is down, will reconnect automatically when it is back up. [19:03] [Error] Connection to server chat.freenode.net (port 8001) lost: Unknown error. At this point, konversation didn't reconnect automatically, although actually claimed. Performing the first manual connection attempt then fails: [19:23] [Info] Looking for server chat.freenode.net (port 8001) ... [19:23] [Info] Server found, connecting... [19:23] [Info] Connected; logging in... [19:23] [Notice] -niven.freenode.net- *** Looking up your hostname... [19:23] [Notice] -niven.freenode.net- *** Checking Ident [19:23] [Notice] -niven.freenode.net- *** Couldn't look up your hostname [19:23] [Error] Connection to server chat.freenode.net (port 8001) lost: Unknown error. [19:23] [Info] Network is down, will reconnect automatically when it is back up. The second attempt is successfull: [19:23] [Info] Server found, connecting... [19:23] [Info] Looking for server chat.freenode.net (port 8001) ... [19:23] [Info] Connected; logging in... [19:23] [Notice] -niven.freenode.net- *** Looking up your hostname... [19:23] [Notice] -niven.freenode.net- *** Checking Ident [19:23] [Notice] -niven.freenode.net- *** Couldn't look up your hostname [19:23] [Notice] -niven.freenode.net- *** No Ident response [19:23] [Welcome] Welcome to the freenode Internet Relay Chat Network
Reopening with the required log messages.
Thank you. The "Network is down, will reconnect automatically when it is back up." message is displayed when Konversation disconnects in response to a "network down" status event from KDE's Solid hardware information library. So this might be somewhere in your network stack. What network backend do you have selected in System Settings?
Thanks for your reply. You're probably right, it could possibly be a problem in my network stack. Kopete doesn't reconnect reliably either. In my network settings, there is only a "Wicd preferences" item, but no explicit choice for a network backend. Where exactly would I choose the network backend?
Should be "Information Sources" in System Settings, and then "Network Management Backend". There's a Wicd one selectable here even though I don't have Wicd installed, so you might be lucky ...
Thanks, I've found it! Even though I switched to Wicd as my "Network Management Backend" now, the reconnection problem is still present in Konversation and Kopete. So I figure the problem might be related to the Wicd solid integration...
Probably, yep ... The only thing I can think of from the Konvi side is the following bug that has been fixed in the dev version since 1.3.1, quoting the changelog: * Fixed a regression that could cause an endless loop of reconnection attempts when issuing a reconnect order to an established connection and the time needed to establish the new connection was longer than the configured reconnection delay. It would also cause confusing status mes- sages to be shown in the connection status tab. But that's a relatively obscure case, and if you're having problems with Kopete too it's more likely to be something outside of Konvi, I'd say. To be sure you could try the dev version of course, which is stable. I'm kind of tempted to close this as NEEDSINFO at this point because I'm not sure what else to do on the available data :). What are your thoughts ...?
I'll build the v1.3 branch and see if the problem is gone. If it's still there, I'd reassign to solid to keep the history of the conversation. What do you think?
Sounds good to me. You'll need to build the master branch though; there's no 1.3 branch. Don't worry however, we keep master stable at all times.
Alright, I've compiled master now. At a first glance, it looks like problem #2 is solved, where a manual connection attempt does not succeed in all cases. I'm closing this bug as fixed because the other problem of not reconnecting automatically is probably related to Solid. Thanks for your help!