Bug 726902

Summary: Error for refresh of directory "INBOX"
Product: [Fedora] Fedora Reporter: Thomas Meyer <thomas.mey>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: 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-08-01 06:27: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:
Attachments:
Description Flags
red error message none

Description Thomas Meyer 2011-07-30 14:54:32 UTC 
Description of problem:
After resume from suspend to ram evolution shows everytime the red error message box with the text "Fehler bei »Ordner »INBOX« wird aufgefrischt«. Server-Verbindung unerwartet getrennt:Die Verbindung wurde vom Kommunikationspartner zurückgesetzt"

I need to press "discard" for every mailbox I have defined, each time the computer resumes from suspend to ram.

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

How reproducible:
always

Steps to Reproduce:
1. start evolution
2. suspend to ram and resume
3. see error message shown
  
Actual results:
error message is shown

Expected results:
no error message should be displayed, as the loss of the network connection is correct for the suspend to ram and resume cycle.

Additional info:
Comment 1 Thomas Meyer 2011-07-30 15:13:45 UTC 
Created attachment 515978 [details]
red error message
Comment 2 Milan Crha 2011-08-01 06:27:51 UTC 
Thanks for a bug report. Evolution is sort of known to not operate with suspend well. A similar issue was reported recently, as bug #706413, thus I'm marking this as a duplicate of it. In the corresponding upstream bug were done some relevant changes in the code too.

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