Please add the latest version to testing or extra.

1 members found this post helpful.

Yeah I noticed that also. It's just not as peppy as FF21.

FWIW, ff16.0.2 is the best, most-stable firefox I've yet encountered.

The ff17 that comes with Scientific Linux is crap (crashes twice a week, exhibits weird bugs), as was the ff17 that Ubuntu12 was using for a while.

The ff18, ff20, and ff21 I've tried have been more stable and less buggy than ff17, but still can't reach ff16.0.2's level of excellence (about 45 days between restarts, with five to eight windows open and hundreds of tabs, and very few problems until about the 40th day).

I'm not trying to say what Slackware should or shouldn't package, but if stability is your priority, you might want to "downgrade" to 16.0.<something>.

The ESR version seems like a significant step backwards as I've used it. I'm going to watch and see if it's chewing up a lot of memory. When I've been running it all day it seems to get progressively slower.

The problem is oxygen-gtk is a theme that is inherently bug prone. The bug is not in Firefox but oxygen-gtk.

Oxygen-gtk causes many other subtle issues and I personally think it shouldn't be included in Slackware, or shouldn't be considered more important than key pieces of software when it has a bug, which it will almost certainly have plenty of.

Oxygen-gtk is not conformant to gtk theme standards, it uses various methods that are not really supported to try to get closer in appearance to oxygen than a conformant theme could.

For example this bug report might be related to this problem

https://bugs.kde.org/show_bug.cgi?id=318891

Notice the developer doesn't want to try and figure out if there is a bug in glib which his theme is dependent on, and which a good upstream would try. He then says

"Oxygen-GTK, unfortunately, has many such invalid assumptions (but we might not know of their invalidity), which it has to do in order to implement the features we need. It's just a matter of complexity of features we put into it."

This is the politic way of saying, we use undocumented and unsupported "features" to create our theme, if we report this "bug" in glib, it will go nowhere because we aren't using gtk themes properly.

I used oxygen-gtk in xfce in Slackware14 initially because I like some aspects of oxygen, and this theme I liked even better than Oxygen, this was my first time to use it, I never bothered with it when I used KDE or xfce in Arch. I had some weird an not very reproducible glitches that I blamed on Slackware, but then I changed my theme because I got bored, and had no such problems, then went back to oxygen-gtk and again had subtle issues.

I personally think oxygen-gtk shouldn't be included in Slackware, and should be in extras or a simple Slackbuild. I think it is very bad idea to downgrade one of the more popular and important pieces of software to a version older than Slackware 14 shipped with because we don't want to delete a stupid theme, especially a theme that is inherently buggy because it is non-conformant to the themeing rules.

Some people want the ESR version of Firefox, that seems a separate issue, as I'm sure just as many of us want the latest release. I think it would be nice for both to somehow be available.

3 members found this post helpful.

17.0.7 > 15.0.1

Again, I think that the "rapid release" model just doesn't fit with Slackware. It would fit with Fedora or Ubuntu. Updating versions so often pretty much guarantees breakage and not only in add-ons. I couldn't handle it, so I will continue to use ESR no matter what Slackware uses.

1 members found this post helpful.

Running Firefox ESR on all my machines as well as on my client's desktops and workstations. So far, not a single crash report. Works perfectly.

1 members found this post helpful.

I've had FF 22 crash several times on Slackware-current (32 bit) while using XFce. I'm going to evaluate a few other browsers for the time being. Opera is running well so far.

ESR has been working ok for me, apart from a few add ons not working correctly with this version. I would prefer to be running 22.0, but can survive with ESR until SW 14.1 comes out.

I tried to make the jump over to seamonkey again, because that has been updated to the latest version correctly, but the Lightning plugin doesn't work with seamonkey-mail for some reason. Bloody plugin version numbering..

Lightning version 2.2b1 works with SeaMonkey 2.17:
https://addons.mozilla.org/en-us/sea...ning/versions/

Thanks for the link

No problems on my machine either and I do like the idea of sticking with the ESR as it seems more in line with the Slackware philosophy. Like I said earlier it seems a tad slower than FF21 but stability is more important to me anyway.

I've moved over to ESR as well. Just had another crash on 22.

1 members found this post helpful.

No problems with 22 at all. For me it wouldn't matter if Slackware comes with the current version or ESR, since one or the other will always be available from SBo.

1 members found this post helpful.