Re: I get: SeaMonkey is already running
BIll Spikowski 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? From another thread, responding to this same problem: 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 find it here: C:\Documents Settings\Your Windows User Name\Application Data\Mozilla\Profiles\default\.slt Where '' is a random eight-character string. The file 'parent.lock', if present, should be in the folder '.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. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
I get: SeaMonkey is already running
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 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: I get: SeaMonkey is already running
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? From another thread, responding to this same problem: 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 find it here: C:\Documents Settings\Your Windows User Name\Application Data\Mozilla\Profiles\default\.slt Where '' is a random eight-character string. The file 'parent.lock', if present, should be in the folder '.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. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: I get: SeaMonkey is already running
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. 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) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: I get: SeaMonkey is already running
goodwin wrote: On 06/24/2013 11:54 AM, goodwin wrote: 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? /SN/ /SM/ Yeap, that's my sus[icion, goodwin, and it seems Mike C has given the OP the good oil!! -- Daniel User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101 Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130502201647 or User agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022815 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: I get: SeaMonkey is already running
On 06/24/2013 11:54 AM, goodwin wrote: 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? /SN/ /SM/ ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: I get: SeaMonkey is already running
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. -- Bill Davidsen david...@tmr.com We are not out of the woods yet, but we know the direction and have taken the first step. The steps are many, but finite in number, and if we persevere we will reach our destination. -me, 2010 ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: I get: SeaMonkey is already running
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
