(old)Puppy Linux Discussion Forum

Mercedes350se wrote:... I have since found that modifying userChrome.css gives the results I want.
...

An even simpler method is to find the existing userChrome.css file and move it to /usr/local/seamonkey/profile/chrome, open as text and change the 9 in the line:

font-size: 9pt !important;

to whatever size suits.

I am finding now it seems to take forever for seamonkey to start. Once started everything is fine. I thought it may be something to do with cache size but reducing it to a small value has not improved things.

Any ideas?

Mercedes350se wrote:

I am finding now it seems to take forever for seamonkey to start. Once started everything is fine. I thought it may be something to do with cache size but reducing it to a small value has not improved things.

I've noticed the same thing...currently running SM 1.1.11 and 2.12.1 in Puppy Linux 4.1.2.
The latter requires lots of overhead (especially compared to the 1.x series).
But they all do anymore, it seems.

Dewbie wrote:Mercedes350se wrote:

I am finding now it seems to take forever for seamonkey to start. Once started everything is fine. I thought it may be something to do with cache size but reducing it to a small value has not improved things.

I've noticed the same thing...currently running SM 1.1.11 and 2.12.1 in Puppy Linux 4.1.2.
The latter requires lots of overhead (especially compared to the 1.x series).
But they all do anymore, it seems.

This seems to help with the slow start issue;

2.13 on lucid 5.28:

http://en.kioskea.net/faq/13084-seamonk ... of-webpage

Thank you but that link seems to be related to slow page loads rather than seamonkey itself starting very slowly.

Like you Dewbie I still have my 1.1.16 install. Given that there is only one site where 2.13.2 is really necessary I think I will go back to 1.1.16 for my general browsing 'experience'.

first use the steps in this thread
http://www.murga-linux.com/puppy/viewtopic.php?t=72301
except I used the glibc's - 2.10 (Not the debian libc 2.11) from here and dbus and dbus glib
http://412collection.co.uk/system.php#ug

MOST Important
I installed Gcc 4.2.2.1 from here
http://distro.ibiblio.org/puppylinux/pet_packages-4/

Finally download seamonkey and unzip to opt from here
http://www.seamonkey-project.org/releases/#2.20

Copy the plugins folder from seamonkey 1.12 folder to the mozilla folder eg. /usr/lib/mozilla then copy libflashplayer.so to this folder. Archived versions available here http://helpx.adobe.com/flash-player/kb/ ... sions.html. Use pupzip to extract libflashplayer.so to this plugins folder.

Yes folks it is a rough method but it works.

Updating must be done manually by downloading new version from seamonkey site as seamonkey's updater requires newer version of GTK.

Gtk cannot be updated as this will break jwm so please don't attempt this.

Have fun

Darren

Is it the newer Flash that causes problems and requires all this patching? I've updated Seamonkey several times in Lucid and once in Precise, just by downloading Mozilla's generic Linux version, installing it, and pointing /usr/local/bin/defaultbrowser to it. I'm using 2.15 on Lucid and (IIRC) 2.17 on Precise, with no problems, other than the bloated size of the binaries.

I don't think I've updated Flash, though. Lucid is at 10.2 r153, which mostly works for me.

@darry1966:
In 3.01, I put all the plugins in /usr/lib/seamonkey/plugins.
Then I make usr/lib/mozilla itself a symlink to /usr/lib/seamonkey/plugins.
This reduces bloat, since the symlink is 0 bytes...


ahoppin wrote:

Is it the newer Flash that causes problems and requires all this patching...I'm using 2.15 on Lucid and (IIRC) 2.17 on Precise, with no problems...

You're running newer Puppies, which don't have the same limitations as pre-4-series.

Dewbie wrote:@darry1966:
In 3.01, I put all the plugins in /usr/lib/seamonkey/plugins.
Then I make usr/lib/mozilla itself a symlink to /usr/lib/seamonkey/plugins.
This reduces bloat, since the symlink is 0 bytes...


ahoppin wrote:

Is it the newer Flash that causes problems and requires all this patching...I'm using 2.15 on Lucid and (IIRC) 2.17 on Precise, with no problems...

You're running newer Puppies, which don't have the same limitations as pre-4-series.

Thankyou Dewbie I appreciate of refinement to my methods - sounds way more efficent.

What is the correct location for userChrome.css in seamonkey 2.22?

The power of the 'net!

Correct location is

~/.mozilla/seamonkey/something.default/chrome/userChrome.css

HTH someone else.