i currently have slack 14 on a vm (virtualbox), firefox22 from current runs fine.

edit: as i now looked at the bug link ive seen "x86_64".. so ff21 crashes on slack 14 64bit?! i run 32bit on my vm and plan to run 32bit if i get slack installed on my routerbox. could be a 64bit compile problem?

I've updated my system from ff21 to ff17esr, however, FireFox seems to now be running slower. Any one else with the same problem?

Going with the ESR branch for -stable is a sane choice and fully support that. Although this decision should have been made as Firefox 17 was the most current version.

I also don't know if this will help, but when I saw the changelog I did download Firefox 22 directly from the Firefox site. I am running a stock Slackware 14 system on my laptop and I am using KDE. I removed the mozilla-firefox package and extracted the Firefox download. It is running just fine, no crashes (at least not yet).

Regardless of that, I do see that the ESR version probably more closely aligns with Slackware's philosophy. I have a need/desire to stay on the latest versions, but I can easily deal with that myself.

Thank you, but I would prefer a methodic way

The only solution I found was to compile Firefox 21.0 using Slackware 14's SlackBuild and generate a slackware package.

If anyone is interested to "down-upgrade" from 17.0esr to 21.0, you can download the slackbuilds from here (if you don't have it in your slackware tree):

32 bits: http://mirrors.slackware.com/slackwa...zilla-firefox/
64 bits: http://mirrors.slackware.com/slackwa...zilla-firefox/

Be sure to download everything but the source of 15.0. Then you download the source of 21.0 from here:

ftp://ftp.mozilla.org/pub/mozilla.or...s/21.0/source/

Now you only have to run the mozilla-firefox.SlackBuild script and "upgradepkg" the generated package file.

I heard that building Firefox is long and complicated. It has scared me off trying to do it myself. How long did your build take (machine specs too, if poss.)?

Building Firefox is long but NOT complicated, however, there are binaries:
http://download.cdn.mozilla.net/pub/...efox/releases/

Suit yourself. These packages were taken from one of Slackware's mirrors.
seems pretty methodic to me ;-)

that way i could also build my own 22,23 etc version as this is whats done by volkerdi/the slackteam?? just in case esr come to current too.

Pat,

I use Slackware 14.0. I don't use KDE often but I have 4.10.1 installed. I made a 22.0 package using the old build script and premade Firefox binary package. 22.0 runs fine for me.

I realize 14.0 came with 4.8.5.

It also came with Firefox-15.0.1.

I'm already using Firefox and Thunderbird ESR since January.
There is no big difference, just some interface improvements.
I like the new "Downloads" window from Main Release, in ESR we have the old one,
but the main release number version is amazing, at Christmas it must be 30 or more

You are right!

I compiled in a Intel Core 2 Quad 2.40GHz, 4GB RAM. The first time I tried it was taking more than 2 hours with full ram + 1GB of swap! I aborted it, and modified the slackbuild script to use "make -j 4" to compile in parallel. It took "only" 54 minutes using ~ 3GB ram.

(BTW, is there a better way to make a slackbuild compile in parallel?)

1 members found this post helpful.

Add your preferred options to the environment variable MAKEFLAGS.

1 members found this post helpful.

with SlackBuilds.org scripts generally passing MAKEFLAGS (like MAKEFLAGS=" -j8 ") works, but the official slackbuilds in Slackware use NUMJOBS in the same way.
BTW, in some of them it's explicitly disabled (because not supported).

1 members found this post helpful.