Bug 669589

Summary:	KDE's Konversation Doesn't Reconnect After Connect Failure
Product:	[Fedora] Fedora	Reporter:	Jimmy Wilson <jawilson>
Component:	konversation	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	rdieter, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-16 19:54:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jimmy Wilson 2011-01-14 04:16:11 UTC

Description of problem:

Konversation doesn't reconnect after network failure.  In my case, it is a VPN connection specifically, and this connection is required for me to reach the IRC server.  If the VPN connection dies while Konversation is connected, once Konversation realizes it has been disconnected, the following two messages scroll forever in the IRC server tab:

[22:11] [Error] Connection to server <host> (port 6667) lost: Unknown error.
[22:11] [Info] Trying to reconnect to <host> (port 6667) in 10 seconds.
[22:11] [Info] Looking for server <host> (port 6667) ...
[22:11] [Error] Connection to server <host> (port 6667) lost: Unknown error.
...

Previous versions of Konversation handled this.

Version-Release number of selected component (if applicable):

rpm -qa | grep konversation returns:

konversation-1.3.1-2.fc14.i686

How reproducible:

Everytime when the VPN/network connection dies.

Steps to Reproduce:
1. Connect Konversation to an IRC server (via VPN in my case).
2. Let the VPN/networking die or wait until it does.
3. The logs above scroll forever even after the VPN/network connection is restored.

Comment 1 Fedora End Of Life 2012-08-16 19:54:53 UTC

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping