Bug 437642 - pidgin doesn't reconnect immediately after a network status change
Summary: pidgin doesn't reconnect immediately after a network status change
Keywords:
Status: CLOSED DUPLICATE of bug 333351
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-15 17:15 UTC by Andrea Dell'Amico
Modified: 2008-03-15 17:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-15 17:31:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.