I get: SeaMonkey is already running

[Mike C]

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?
It may be that SeaMonkey didn't shut down properly on some
occasion. If that happens, a file called 'parent.lock' is created,
which prevents another instance of SeaMonkey from running.
With SeaMonkey closed, locate the SeaMonkey 1.x profile, you should
C:\Documents & Settings\<Your Windows User Name>\Application
Data\Mozilla\Profiles\default\xxxxxxxx.slt
Where 'xxxxxxxx' is a random eight-character string.
The file 'parent.lock', if present, should be in the folder
'xxxxxxxx.slt', if it is delete it. You should then find that you
will no longer get the message that SeaMonkey is still running and
you should be able to run SeaMonkey 2.7. Note that SeaMonkey 2.8 is
now available, so I would suggest installing that, rather than
v2.7.
I hope that helps.
Regards,
Dave.

That worked!
Thanks a lot!!

Now there's a new problem.
I'll start a new thread called:
"Duplicate Emails"

Maybe you'll know the answer on that one.

[Mike C]

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?

Mike C

[BIll Spikowski]

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?
It may be that SeaMonkey didn't shut down properly on some
occasion. If that happens, a file called 'parent.lock' is created,
which prevents another instance of SeaMonkey from running.
With SeaMonkey closed, locate the SeaMonkey 1.x profile, you should
C:\Documents & Settings\<Your Windows User Name>\Application
Data\Mozilla\Profiles\default\xxxxxxxx.slt
Where 'xxxxxxxx' is a random eight-character string.
The file 'parent.lock', if present, should be in the folder
'xxxxxxxx.slt', if it is delete it. You should then find that you
will no longer get the message that SeaMonkey is still running and
you should be able to run SeaMonkey 2.7. Note that SeaMonkey 2.8 is
now available, so I would suggest installing that, rather than
v2.7.
I hope that helps.
Regards,
Dave.

[Mike C]

Post by Mike C
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.

Try this:

To fix this, open the profile folder and delete the file,
"parent.lock" (Windows)
"lock" and ".parentlock" (Linux), or
".parentlock" (Mac OS X)

[Daniel]

Post by Mike C
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?

/SN/ /SM/

Yeap, that's my sus[icion, goodwin, and it seems Mike C has given the OP
the good oil!!

[goodwin]

Post by Mike C
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?

/SN/ /SM/

[goodwin]

Post by Mike C
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?

[Bill Davidsen]

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.