There may be more difficulties as yet unresolved.
I read this How-To:
>
http://kb.mozillazine.org/Starting_your_Mozilla_application_with_a_specified_profile
And so I tried starting icedove from the command console this way:
>> amenex:~$ icedove -profile "6otj8u2m.amenex05"
>> (process:3558): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
>> (icedove:3558): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::sm-connect after class was initialised
>> (icedove:3558): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::show-crash-dialog after class was initialised
>> (icedove:3558): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::display after class was initialised
>> (icedove:3558): GLib-GObject-WARNING **: Attempt to add property
GnomeProgram::default-icon after class was initialised
There are some [unresolved ?] bugs that are found by searching on that
GLib-Critical line ...
At any rate, there's something that stops icedove from starting (with
whichever profile that I try.)
Here's the error message:
> Profile Missing
> Your Icedove profile cannot be loaded. It may be missing or inaccessible.
But it's still there, unchanged since I last successfully read my icedove
emails this morning. It's the system that can't access my profile.
