Bug 437642

Summary:	pidgin doesn't reconnect immediately after a network status change
Product:	[Fedora] Fedora	Reporter:	Andrea Dell'Amico <adellam>
Component:	pidgin	Assignee:	Warren Togami <wtogami>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	stu
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-03-15 17:31:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrea Dell'Amico 2008-03-15 17:15:16 UTC

Description of problem:

pidgin doesn't reconnect immediatly after a nework disconnection or after a
suspend/resume cycle.

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

Starting from 2.0

How reproducible:
Always

Steps to Reproduce:
1. detach/reattach you network cable, or perform a suspend/resume cycle
2. Have NetworkManager running and managing your connection

Actual results:
pidgin doesn't try to reconnect, it always waits for a (long) timeout.
Other applications (evolution, epiphany, liferea) see the network status change
immediatly

Expected results:
Reconnection as soon as the network is available.


Additional info:

Comment 1 Stu Tomlinson 2008-03-15 17:31:18 UTC


*** This bug has been marked as a duplicate of 333351 ***