Re: [Evolution] Need help identifying files

[Pete Biggs <pete biggs org uk>]

> One of our Ubuntu 12.04 (64-bit) boxes (my wife's) has apparently
> experienced a corrupted database file - when she tries to retrieve
> mail from Evo 3.2.3, she gets the messages:          
>
> ERROR WHILE GENERATING MESSAGE LIST
>
> DATABASE DISK IMAGE IS MALFORMED.
>
> I have done considerable research, to the extent of finding some blog
> posts which deliver what looks like a workable fix. But the problem
> I have now is that everything I have found relates to versions earlier
> than what we have, and to 32-bit versions, in which the name of the db
> is something different than what it apparently is in the newer version.
>
> I have verified that the file in question, folders.db, is present
> in 32-bit versions, but does not show up in our 64-bit versions.
> Clearly Evo has changed the name, and probably the location as well,
> because all the paths are definitely different. For example, rather than
> the former practice of the ".evolution" directory appearing directly
> under "/home/[user]", it's now under /home/[user]/.local/share,and as
> "evolution", not as ".evolution".But in all the dicking
> around I've had to do in Evo, I've yet to locate any usable reference
> as to what Evo names its internals, and where it puts them.
> Does anyone know what the name is for the primary folder database file
> in 3.2.3 under 64-bit 12.04? Better yet, can anyone point me to a
> reference source that would disclose these kinds of internal structures?

The location of the data files is in the FAQ accessed through the
Evolution Help menu (i.e. Help -> Contents).  This gives a broad view of
where the data files are located in your version of Evo. Note that the
location of those files changes through the various versions - but they
are NOT dependent on 32 vs 64-bit.

If you want to find out where the folders.db files are, you can use
either the 'find' command or 'locate' - just do 'locate folders.db' and
it should tell you where they all are.  If your system is crippled such
that it doesn't maintain a database of the file locations, then you can
use the command 

  find . -name 'folders.db' -exec ls -l {} \;

to find them.  Once you've found the folders.db file, you can check to
see if it's corrupt and possibly fix it using sqlite3 - or alternatively
you can just move the file aside and let Evolution create a new one.

P.