Bug 122401 - Leaving Evolution open for a while generates "Error while 'Scanning folders in "IMAP server XXXX.XXXX.XXX"'
Summary: Leaving Evolution open for a while generates "Error while 'Scanning folders i...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-04 00:51 UTC by Shawn M. Jones
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: 1.4.6-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-11 03:51:15 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Shawn M. Jones 2004-05-04 00:51:39 UTC 
Description of problem:
Welp, evolution generates "Error while 'Scanning folders in "IMAP
server XXXX.XXXX.XXX" messages if left open for a while.

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

How reproducible:
Always, as near as I can tell.

Steps to Reproduce:
1.  Set up evolution to connect to an IMAP server.
2.  Leave it open after you've read a few messages in the INBOX on the 
IMAP server
3.  Leave one of the INBOX messages selected
  
Actual results:
Error while 'Scanning folders in "IMAP server XXXX.XXXX.XXX"':
Operation now in progress
(hostname replaced with XXXX.XXXX.XXX)

Expected results:
These error messages should not appear.

Additional info:
My IMAP server runs Debian Woody WU-IMAP.
Comment 1 Dave Malcolm 2004-09-22 17:31:36 UTC 
Can you still reproduce this bug?  If so, please can you restart
evolution with CAMEL_VERBOSE_DEBUG=1 set, and see if this shows up
anything.
Comment 2 Shawn M. Jones 2004-10-11 03:51:15 UTC 
I cannot currently reproduce this bug.  This appears to have been
fixed by evolution 1.4.6-2 in FC2 release.

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