Le 5 mars 2011, Bernard Mercier a écrit :

But then I got the message that I had probably another SeaMonkey instance
running and that I had to close it first.

Does anyone has the same issue?

Yes, but I got it only once, at the first launch after updating.

How can I correct this issue?

Maybe: make sure again there's no SM running, then remove ~/.mozilla/seamonkey/*.default/lock

--
LL
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to