« previous next »
Pages: [1]   Go Down

Author Topic: Seamonkey problem.  (Read 2848 times)

Offline JohnJS

  • Jr. Member
  • **
  • Posts: 62
Seamonkey problem.
« on: March 05, 2011, 03:32:53 PM »
Using Seamonkey with TCL3.5.
The first time I used it after installation it worked fine. On subsequent attempts to use Seamonkey I get this message:

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.

Can't figure a way to 'close' process. Tried restarting and also shutdown to no avail.
Also get this message after being shutdown overnight.
« Last Edit: March 05, 2011, 03:35:43 PM by JohnJS »
Logged

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Seamonkey problem.
« Reply #1 on: March 05, 2011, 03:51:16 PM »
IMHO debatable if an app which explicitely calls the user for a restart of the system due to overcome its own bugs could be labelled as "malware" in a Linux environment...   :o
Logged
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline thane

  • Hero Member
  • *****
  • Posts: 691
Re: Seamonkey problem.
« Reply #2 on: March 05, 2011, 04:43:20 PM »
It's possible the process got saved to your backup and is getting restarted when you boot.

Try going to Control Panel/System Stats/processes to see if you can see a PID for the unwanted process. Then open a terminal and type "kill [PID]" (no brackets or quotes). If that works, exit all your apps and reboot again with backup. That should replace the old backup file so the process isn't restarted when you boot.
Logged

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Seamonkey problem.
« Reply #3 on: March 05, 2011, 05:37:36 PM »
Mozilla browsers create a lockfile.
Lookin your .mozilla directory and delete it.
Next time close seamonky before shutting down or add the lock file
to .xfiletool.lst.
Logged

Offline JohnJS

  • Jr. Member
  • **
  • Posts: 62
Re: Seamonkey problem.
« Reply #4 on: March 05, 2011, 05:58:48 PM »
Thanks thane and gerald_clark.

Will keep the info handy if the problem returns.

I removed and re-installed seamonkey three times and it seems to work fine now. Don't know if its me but seems to work faster than opera10 with my dial-up modem.




« Last Edit: March 07, 2011, 09:18:19 AM by JohnJS »
Logged

Offline JohnJS

  • Jr. Member
  • **
  • Posts: 62
Re: Seamonkey problem.
« Reply #5 on: March 07, 2011, 09:18:53 AM »
3/7/11:
Worked fine until I started up today. Get the same error as in my first post.
Tried to delete PID from SystemStats/Processes but none related to Seamonkey.
Can't locate .mozilla "lockfile". How is it identified?
Thanks for assistance. Decided to remove Seamonkey and keep Opera10.
« Last Edit: March 07, 2011, 09:34:44 AM by JohnJS »
Logged

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Seamonkey problem.
« Reply #6 on: March 07, 2011, 10:22:43 AM »
It is usually called something like lock or parentlock.
I may be burried somewhere down in the ~/.mozilla directory.
Logged

Offline JohnJS

  • Jr. Member
  • **
  • Posts: 62
Re: Seamonkey problem.
« Reply #7 on: March 19, 2011, 10:37:59 AM »
FWIW Seamonkey with dial-up modem has been working well for about a week now.
I did something close to what thane suggested.
ControlPanel/processes did not show PID for seamonkey.
I just deleted xxx.default from .mozilla/seamonkey, backed up and restarted. Now shows a different xxx.default file.
Seems to have done the trick.
Thanks to all.
Logged
Pages: [1]   Go Up
« previous next »