Date: Fri, 21 Feb 2003 08:38:33 -0500 From: "Brian T. Schellenberger" <bts@babbleon.org> To: David Schultz <dschultz@uclink.berkeley.edu>, Yann Golanski <yann@kierun.org> Cc: ajs@labs.mot.com, freebsd-stable@freebsd.org Subject: Re: Mozilla window won't open after upgrade - FIXED Message-ID: <200302210838.34252.bts@babbleon.org> In-Reply-To: <20030221090930.GA55832@HAL9000.homeunix.com> References: <3E5568AF.1050100@labs.mot.com> <20030221084955.GC12058@kierun.org> <20030221090930.GA55832@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
BINGO!
That did it.
I did
pkg_delete -f fontconfig\*
cd /usr/ports/*/fontconfig
make install
and now it's all peachy.
I will update bugzilla momentarily.
PS:
To Yann Golanski: My mozilla is not SUID root, so that wasn't
the problem I was having, but thank you very
much for the suggestion.
To Darren Pilgrim: It might work to .undef STRIP, but if so it looks
like I'd have to do a rebuild to make it work,
because just doing
make deinstall
make STRIP= reinstall
(or make deinstall; edit to add .undef STRIP;
make reinstall)
didn't do it, so it looks like STRIP, if it does
make it strip, does do it "in place."
Since the above fixed the problem I saw no reason
to take the time for a full rebuild.
On Friday 21 February 2003 04:09 am, David Schultz wrote:
| Thus spake Yann Golanski <yann@kierun.org>:
| > Quoth Brian T. Schellenberger on Thu, Feb 20, 2003 at 20:48:51
| > -0500
| >
| > > First mozilla-bin gets a segv, Then the script that invokes it
| > > fails to notice that it failed and doesn't give a useful message.
| >
| > I think I had the same problem. Does mozilla run as root? If it
| > does, run it as root (via sudo) and then chown/chgrp the
| > $HOME/.mozilla to your user/group and that should work from there
| > onwards. Then again, it may have been another problem I was
| > having... Long life Mozybug.
|
| Yes, mozilla quite annoyingly traps SIGSEGV. Moreover, it is
| started by a chain of three shell scripts, which means it takes
| yet another step to debug. For me, reinstalling some font-related
| port---fontconfig, I think---solved the problem. It didn't help
| that a recent mega-commit changed a bunch of paths for X11 ports,
| so I backed out my ports collection to 2/17 for now. If things
| don't compile, you might try that, too.
--
Brian, the man from Babble-On . . . . bts@babbleon.org (personal)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302210838.34252.bts>