GNOME Bugzilla – Bug 735433
Error while performing operation - Empty cache file
Last modified: 2015-03-03 19:02:19 UTC
Hi :) I see the following message rather often (maybe twice a day), but I do not have an idea how to trigger it: Error while performing operation. Empty cache file: /home/nicolas/.cache/evolution/mail/1400151892.7315.2@xyy/folders/INBOX/cur/32/3695173 The message is displayed in the "notification area" above the message list and the mail preview. It seems to be a quite "generic" message and I therefore used Google to have a look for suggestions of other users. I then found this message from Milan: https://mail.gnome.org/archives/commits-list/2014-May/msg01485.html Note: I have a good/stable internet connection and I don't cancel any actions. I'm not sure, if the patch mentioned is already in 3.12.5 (which is my current version). If so the problem probably still exists, otherwise you can close this bug and I'll wait for 3.14 and check if the problem still exists there. In any case - If I can somehow help you to find the problem just let me know what I should provide (I'm perfectly find building evo from source or fiddle around with gdb if that helps in any way). Thanks for your work! Kind regards, Nicolas
I'm experiencing this same issue: Error while performing operation. Execution of filter 'Junk check' failed: Empty cache file: /home/me/.cache/evolution/mail/1257474335.3333.26@me/folders/INBOX/cur/35/107995 I see this multiple times throughout the day. I've tried closing Evolution, deleting /home/me/.cache/evolution/mail/, and letting it repopulate, but same issue. I am using Evolution 3.12.7 under Xubuntu Utopic (amd64).
I'm still experiencing this same issue at least ten to twenty times a day. Every time this happens, all message and spam filters break temporarily until I restart the client.
I also experience this constantly throughout the day. It is very annoying! I too have tried deleting my .cache folder. I've also tried deleting and recreating my account through evolution. No change. This is fairly recent (started when I upgraded to fedora 21) I am running 3.12.10 on Fedora 21 (evolution-3.12.10-1.fc21.x86_64).
My distro recently updated my Evolution from 3.12.7 to 3.12.10 and it's still doing this.
Thanks for a bug report. You are right, it's still there. I'll mark this as a duplicate of a newer bug report, because that one has more detailed information and contains some investigation too, with a possible finding what causes the error. *** This bug has been marked as a duplicate of bug 737468 ***
Thanks Milan. =)