Bug 990571 - evolution retrieving message forever if one quickly deletes two emails
Summary: evolution retrieving message forever if one quickly deletes two emails
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 19
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: 2013-07-31 13:28 UTC by David Juran
Modified: 2013-07-31 15:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-31 15:27:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 705206 0 None None None Never

Description David Juran 2013-07-31 13:28:27 UTC
Description of problem:
If I quickly delete two (or more) email messages, by quickly pressing the delete key twice, evolution will then hang forever, just saying "retrieving message XXX" in the preview window.
The only way to proceed is to click on some other message and then going back to the message that previously didn't load. The message will this time load.

Version-Release number of selected component (if applicable):
evolution-3.8.4-1.fc19.x86_64
evolution-data-server-3.8.4-1.fc19.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Press delete twice
2. The next unread message will not load
3.

Additional info:
I have a CAMEL_DEBUG=all logfile (78 MB) available upon request.

Comment 1 Milan Crha 2013-07-31 15:27:59 UTC
Thanks for a bug report. I do not think it downloads the message forever, it's rather a stale message in the preview panel (note the status bar doesn't mention the same operation). I noticed something similar when only reading mails, the message is not loaded (using IMAP+) and the preview pretends it being received. As this is not fedora specific, I'm moving it upstream. Please see [1] for any further updates.

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


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