On Thu, 14 Oct 2010 01:53:32 +0100 Ken Moffat <[email protected]> wrote:
> I always use --disable-gnome-vfs. I've got that because when I > first build firefox, I don't have gnome-vfs installed and I'd > assumed I needed that switch. [ I use the same script if I have to > upgrade to a later version ] I tried --disable-gnome-vfs but strangely it had no effect > > Adding an extra library after you've built something doesn't > *normally* affect the existing packages, unless it adds a plugin. > > Is this a released version of firefox ? Have you patched cups for > the locking fix ? > No, it's current mercurial versions of Firefox though apparently also affects versions of Firefox frome the 3.6 stable line. What is the locking fix for cups? Further googling on the subject today led me to: http://www.linuxquestions.org/questions/slackware-14/slackware-13-1-first-batch-of-updates-print-crash-on-firefox-and-thunderbird-816854/page2.html http://www.cups.org/str.php?L3606 https://bugzilla.mozilla.org/show_bug.cgi?id=573039 And the solutions which are to downgrade to cups-1.4.3 or (the solution I chose) recompile cups with --enable-gnutls --disable-openssl It's a bug in Firefox, not gnome-vfs or cups. Weird that it isn't triggered until gnome-vfs is installed. Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
