On Mon, Nov 17, 2014 at 05:32:22PM -0500, Richard wrote:
> 
> I think I successfully built firefox-32.0.1 in
> blfs-7.6, but it is terribly slow, to the point
> of being unusable. I have tried various things
> that I saw on the web, such as: adding myself
> to the video group, enabling pipelining, checking
> that DRI is enabled, re-setting firefox. Nothing
> seems to help. Firefox loads alright and I
> can load web pages, but some sites (for example,
> www.zillow.com) take forever to load, and they
> don't really function correctly when they are
> loaded (for example the up/down and pg-up/pg-down
> keys don't seem to work properly).
> I am wondering if anyone else is having these
> problems with firefox, or has any suggestions.

 Appears to load here (I'm running 33.0, this is on my netbook) but
I agree that pg up/dn do not seem to work - dragging the slider down
with the mouse works.  As to whether the site works, no idea - I
don't have a login there, nor any interest in it.
> 
> Also, I heard that the Berserk SSL bug has
> been fixed in firefox-32.0.3:
> 
> >https://www.mozilla.org/security/announce/2014/mfsa2014-73.html
> 
> I'm wondering if users should upgrade if
> they have firefox-32.0.1. If we do upgrade,
> does anyone know if we can use the same
> dependencies as for firefox-32.0.1 in the
> BLFS-7.6 stable book? I saw a discussion
> about upgrading gcc or changing optimization
> levels, but assuming that is addressed,
> can the other dependencies be the same?
> 
> Richard

 In general, upgrade to the next major version whenever it is
released - they all appear to fix vulnerabilities.  For the fixed
vulnerabilities, I usually look at the mozilla.org release notes -
most point releases do not add new vulnerability fixes, although the
release notes need to be compared to the previous notes for that
major version to work out what is new in this point release.
If you are going to upgrade, check the development book -
particularly for altered commands or new dependencies.

 The dependencies listed in the BOOK are only the current versions
which were tested - BLFS does not normally update old releases.  But
if you use system nss or nspr you SHOULD update those, firefox binary
releases will include newer nss, and occasionally nspr, when
appropriate - but they might still be using an old version such as
3.16.  Occasionally, a newer version of another package may be
needed, but usually I would try first with the existing versions.

 Whenever I update my current systems, and those old systems which I
regard as "minimally supported" - i.e. I ought to be able to use
them (e.g. if I want to test a newer version of an old supported
kernel release, or perhaps to restore '/' in chroot from a backup if
things went badly) I usually update sqlite, and always update nss,
and nspr if that has a newer version, before building firefox.  That
is probably more than you wanted to know, my point is that _you_ are
the only person responsible for security on _your_ LFS/BLFS systems
so you will have to thinks things through and make a decision.

ĸen
-- 
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to