GNOME Bugzilla – Bug 554990
Evolution Mail and Calendar: Corruption in folder. Af...
Last modified: 2009-04-13 06:18:20 UTC
Corruption in folder. After erasing all messages, I am unable to delete it. Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.24.0 2008-09-22 (Ubuntu) BugBuddy Version: 2.24.0
*** Bug 554991 has been marked as a duplicate of this bug. ***
*** Bug 554992 has been marked as a duplicate of this bug. ***
cgb, Can you be ellaborate? What error does it report?
I had a number of problems after upgrading to version 2.24.0 (as in Ubuntu Intrepid). My mail was imported from the previous version but I believe that the process did not run properly. As a consequence, there were a number of mails in my trash folder that did not relate to any message in any other folder. Trying to expunge other folders leaded to either crashes, error messages or, simply, nothing. I could finally solve the problem by deleting the folders.db file by hand. It was recreated again and everything worked from that point onwards. I guess that such file keeps track of "deleted" but "not expunged" messages. Perhaps this operation is not performed properly after an upgrade. Perhaps you could "expunge" messages after the upgrade before importing the mail folders.
you deleted folders.db from which folder? It is possible that migration was buggy, did the summary recreation helped you? Are there any other issues that you face now ? Incase you see a crash, can you get me the traces?
From ~/.evolution/mail/local I think that folders.db in that directory was not created properly during the upgrade. After I erased it: 1) Some erased messages appeared in my folders again (not big problem). 2) I could clean up the Trash folder. 3) The file was recreated.
>1) Some erased messages appeared in my folders again (not big problem). Even now? Does this mean that your deleted mails are appearing now?
Any updates? 2.24.3 has lots of fixes, can you try with it?
Can you please try in 2.24.4 or 2.24.5 and report back, thanks.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.0 or later), please reopen. thanks in advance.