On 06/24/2013 09:35 AM, Bill Davidsen wrote:
Mike C wrote:
When I try to open SM I get:
SeaMonkey is already running, but is not responding. To open a new
window, you
must first close the existing SeaMonkey process, or restart your system.
BUT, It's NOT running!
This even happens in safe mode.
And with a fresh re-boot.
Anyone know the answer?
No, but I know a new (related) question, why doesn't "-new-instance"
make it ignore the problem. Acording to help that's exactly what it
should do. And I believe I've used command line options to open a new
remote version as well, but don't have time to research it for you. Take
a look at the "-remote" command values, see if that gives you a
workaround if you ever really do have a running process.
I don't use SN (yet) but am curious here - does SM use the parentlock
file as TB and FF do?
Might that be in play here?
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
