SeaMonkey Quits on it's own!

amacg3 · 06-30-2009, 12:58 PM

Hi Spongedaddy,

Sorry to hear you are still having the same problem, I don't know what it could be, all I can tell you is my issue went away (so far) since unpgrading to 4.2.

spongedaddy · 07-01-2009, 08:23 AM

I have 4.00 running as a full HD install on my ancient Dell OptiPlex and have never had the problem. I'm using the 4.00 live CD on the laptop.

Could it be a live CD issue? Just wondering...

And it's not really a biggie since it has only happened once for me. I may upgrade one of these days.

Cheers!

vance.waylon · 07-18-2009, 06:27 PM

The long and short of this is compatibility, assuming you didn't break anything. Different (older and current) versions of Puppy do not always mesh well with versions of Seamonkey. Like noted earlier, try uprgading your Seamonkey. If the problems arise, persist or worsen, downgrade the Seamonkey. If that fails upgrade the Puppy itself, keeping in mind that there is no "easy" way to simply downgrade your Puppy! Once Puppy is upgraded try the whole Seamonkey update fiasco again.
Flash could also be the culprit. I know this is a shot in the dark, but when you experienced a crash... do you remember how many instances, if any, there were of flash? A simple flash overload will cause any browser to crash and burn. What version Flash id running? Personally, once I upgraded to Flash 10 my browsers began crashing. Ive since downgraded back to Flash 9 and the browsers are back to stable.
As for installing the Seamonkey upgrade in Puppy, download the archive from the official site, unpack it, and click the installer. Almost too easy, it's sort of uncomfortable. By default SM wants to install to usr/bin (or somewhere like that) but you need it to go to the current SM directory (should be /usr/lib/seamonkey-xXx) to overwrite the current install (so you dont have two monkeys!). Honestly, I would recommend getting a .pet package of any program for beginners (or for slackers) and install it through the Pet package manager. This way helps resolve the dependencies. Although in this situation Seamonkey comes complete and is safe to install manually.

otropogo · 07-19-2009, 01:06 AM

Quote:

Originally Posted by vance.waylon

The long and short of this is compatibility, assuming you didn't break anything. Different (older and current) versions of Puppy do not always mesh well with versions of Seamonkey.

Have had the problem in three successive versions of Puppy, and have never tinkered with Seamonkey, have only used the version that came bundled.

Quote:

Like noted earlier, try uprgading your Seamonkey. If the problems arise, persist or worsen, downgrade the Seamonkey. If that fails upgrade the Puppy itself, keeping in mind that there is no "easy" way to simply downgrade your Puppy!

As mentioned earlier - I don't know how to upgrade Seamonkey without a .pet.

Quote:

... Flash could also be the culprit. I know this is a shot in the dark, but when you experienced a crash... do you remember how many instances, if any, there were of flash? A simple flash overload will cause any browser to crash and burn. What version Flash id running?

Personally, once I upgraded to Flash 10 my browsers began crashing. Ive since downgraded back to Flash 9 and the browsers are back to stable.

Have never upgraded Flash, and don't have a clue as to how many instances were running when Seamonkey crashes. But it's crashed after having opened only one window on a single site since booting.

Quote:

As for installing the Seamonkey upgrade in Puppy, download the archive from the official site, unpack it, and click the installer. Almost too easy, it's sort of uncomfortable. By default SM wants to install to usr/bin (or somewhere like that) but you need it to go to the current SM directory (should be /usr/lib/seamonkey-xXx) to overwrite the current install (so you dont have two monkeys!).

Yeah, sounds much too easy!

Quote:

Honestly, I would recommend getting a .pet package of any program for beginners (or for slackers) and install it through the Pet package manager. This way helps resolve the dependencies. Although in this situation Seamonkey comes complete and is safe to install.

manually.

Sure. So all I have to do is wait for someone to make and post a .pet for the current version of Seamonkey, install it, and then see if it solves the unwanted shutdowns. Great! Thanks a lot. Pretty much what I was thinking myself.

I'm sure all of us "slackers" appreciate your help.

vance.waylon · 07-26-2009, 07:41 AM

I dont want to be rude BUT YOU DONT NEED A PET. In seamonkeys case all you have to do is the same procedure you would do in a windows install. UNZIP the archive into root, inside your extracted folder will be an installer, click on it and an automated "windows style" installation will follow. Puppy comes loaded with Seamonkeys dependencies, so the upgrade doesnt have deps. If it then still crashes and you want to know why, run it from the terminal and read what it says. When you got it working, "dir2pet" and make your own package....newb.

otropogo · 07-27-2009, 09:23 AM

Quote:

Originally Posted by vance.waylon

I dont want to be rude BUT YOU DONT NEED A PET.

Your statement above leaves me wondering why anyone went to the trouble of creating pets for installing Seamonkey 1.1.8, 1.1.11, and 1.1.14...

Quote:

In seamonkeys case all you have to do is the same procedure you would do in a windows install. UNZIP the archive into root, inside your extracted folder will be an installer, click on it and an automated "windows style" installation will follow.

According to the installation instructions on the Seamonkey site, there's at least one major problem with your suggestion. Any existing installation of Seamonkey must be uninstalled before the new one is installed. However, there is, according to everything I've found on the subject, no way of uninstalling any program that comes bundled with Puppy.

So I hope you won't consider ME rude, if I decline to follow your instructions. Web browsing is my main activity with Puppy, and I don't care to mess up my only browser any further on the remote chance that whatever is causing Seamonkey to shut down unexpectedly has been successfully addressed in the latest version.