Hi guys,

Has anyone else got problems getting profiles to work with
the newer seamonkey?

I found that after the initial upgrade from 1.1.18 to 2.0.0
user profiles weren't migrated/imported, so I backed the
upgrade out.

Now with 2.0.3 and a bunch of new vulnerabilities I re-installed
and still can't get a profile migration.. I resorted to giving
up on the idea all together, but even when I erased ~/.mozilla
I still can't get any profiles to work with 2.0.x at all.

Any attempt to start up a second instance with a new profile (-P)
brings up the same profile already in use in the first instance,
and switching profiles via "profile manager" from a running
seamonkey will close the previously open profile to open the
next one ....

Been googling for hours but can't seem to find anything actually
relevant to a resolution of this issue.


Cheers,
Tink

Turns out that for seamonkey 2 to use profiles it's not enough
any more to use a -P <profile name> switch, you have to add a
'-no-remote' if you want to use several instances with different
profiles in parallel.



suggestion on mozillazine

Cheers,
Tink

In addition to the links off the mozilla-zine post, a "quick & dirty"
guide to updating seamonkey 1.1.x to 2.0.x and preserving info like
bookmarks, saved passwords and other settings ...

after you want to
a) create new profiles for seamonkey2 and
b) migrate the old ones over.

(and exit it)

Run it again, it will ask you WHICH old profile you want to migrate.

Repeat for all profiles.



Once you're done, edit whatever means you use to start seamonkey with
a profile to look like
from
to



Cheers,
Tink