Bug 726902 - Error for refresh of directory "INBOX"
Summary: Error for refresh of directory "INBOX"
Keywords:
Status: CLOSED DUPLICATE of bug 706413
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-30 14:54 UTC by Thomas Meyer
Modified: 2011-08-01 06:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-01 06:27:51 UTC
Type: ---


Attachments (Terms of Use)
red error message (58.25 KB, image/jpeg)
2011-07-30 15:13 UTC, Thomas Meyer
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.