Thanks for your suggestions. These did not work. Evolution said (after
removing the folders.db) that every folder was empty.
So, I tried to restore from one of my old backup file that evolution
Evolution started the restore process, and finally came up with the
error message (attached to this mail as a png format file) on its restart.
I had to reboot the machine and restarted evolution assuming that it
would have set everything from the backup file, but nothing seem to have
got registered. It came up with the first time evolution startup screen.
I went to into the mail folder under .local/share/evolution/mail/local
and saw all the restored filenames and folders. However in each folder
under the 'cur' directory, there were filenames with 0 bytes in them.
This means evolution did not restore the backup files properly. It
created folders and files with their respective names, but not the
contents of the files.
I am currently using thunderbird, but badly in need of evolution to work
in Fedora22, so that I can get all my saved emails that are important.
On 20/04/15 12:18, Milan Crha wrote:
On Mon, 2015-04-20 at 11:10 +0100, Nethaji wrote:
> I have installed Fedora 22 Alpha release, kernel 4.0.0-
> Evolution version 3.16.0.
> When I click on any saved mails (including drafts), evolution brings
> up a warning message in the message window (please see attached).
> help would be much appreciated.
all the On This Computer/... messages are stored at
I would guess that the summary of the stored messages (the folders.db
file there) got out of sync with the folder content, despite it's
supposed to recheck the folder content on each start.
I would try to backup the ~/.local/share/evolution/mail/local folder,
then move away the folders.db file from it and let Evolution recreate
it from scratch. Be aware that you may lose some things, like message
labels, by this operation.
On the other hand, if I read the path in the error message properly,
then you've stored your home on some shared network place. Could you
verify that the error message is correct (no such file in that folder)
or that you can read/write to that file when opened from the network