Bug 751211

Summary:	imap ping timeout to a server take to much time
Product:	[Fedora] Fedora	Reporter:	Sergio Basto <sergio>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	15	CC:	lamefun.x0r, lucilanga, mbarnes, mcrha
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-07 07:57: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:
Embargoed:

Description Sergio Basto 2011-11-03 20:51:36 UTC

Description of problem:

early since Fedora 15 I have a laptop sometimes I disconnect from network,
and ping timeout take more than 10 minutes which is very annoying. Sometimes I lose my patience and use killall evolution , but if I wait , evolution close by it self , but every time that I got a network problem , I have to wait arround 10 minutes (I don't count) to get evolution ready again.


Version-Release number of selected component (if applicable):
evolution-3.0.3-1.fc15.x86_64

How reproducible:
I simply create an imap account, and in mail server configuration write wrong name of a server (be sure that doesn't exist at all). 
And try get email . 
 
  
Actual results:
Ping server , round and round many minutes and block evolution.

Expected results:
give a quick error. 

Additional info:

Comment 1 Milan Crha 2011-11-07 07:57:51 UTC

Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=557078

Comment 2 Milan Crha 2011-12-08 08:20:50 UTC

*** Bug 761280 has been marked as a duplicate of this bug. ***