After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 606600 - Error while expunging folder
Error while expunging folder
Status: RESOLVED DUPLICATE of bug 550414
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-01-11 03:12 UTC by Matthew Barnes
Modified: 2010-01-11 03:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthew Barnes 2010-01-11 03:12:43 UTC
Forwarding from a Fedora bug:
https://bugzilla.redhat.com/show_bug.cgi?id=554149

Description of problem:
Periodically, I try to expunge my Inbox of deleted messages and I get an error
message: Error while expunging folder. Clicking on the little warning triangle
in the lower left corner of the window yields a dialog box with the text: Error
while Expunging folder. Summary and folder mismatch, even after a sync. The
deleted messages are not expunged.

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

How reproducible:
Intermittent. I can expunge a few times but eventually I get the error message.

Steps to Reproduce:
1.Fetch some mail
2.Delete a message
3.Type "Ctrl-e" to expunge

Actual results:
Receive warning message about summary/folder mismatch.

Expected results:
Delete messages are expunged.

Additional info:
This seems to have started happening after the most recent evolution update. I
didn't notice this problem for the previous few weeks I'd been using Fedora 12.
Comment 1 Akhil Laddha 2010-01-11 03:22:15 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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