Date: Tue, 11 Feb 2003 21:44:41 -0500 From: stan <stanb@awod.com> To: FreeBSD User Questions List <freebsd-questions@freebsd.org> Subject: Re: Mozilla/Galeon broken after portupgrade Message-ID: <20030212024441.GA12824@teddy.fas.com> In-Reply-To: <1045016579.89844.5.camel@shumai.marcuscom.com> References: <20030211230205.GB7394@teddy.fas.com> <3E498322.5060708@vagner.com> <20030211235035.GA8795@teddy.fas.com> <20030212011954.GA90935@tao.thought.org> <2030.10.0.0.2.1045013765.squirrel@mail.karamazov.org> <1045016579.89844.5.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 11, 2003 at 09:22:59PM -0500, Joe Marcus Clarke wrote: > On Tue, 2003-02-11 at 20:36, Scott A. Moberly wrote: > > > On Tue, Feb 11, 2003 at 06:50:35PM -0500, stan wrote: > > >> On Tue, Feb 11, 2003 at 06:11:30PM -0500, Laszlo Vagner wrote: > > >> > stan wrote: > > >> > > > >> > >I did a cvsup, make world, portupgrade sequence this weekend, and > > >> now both mozilla, and galeon die when started. > > >> > > > > >> > >Any sugestiosn as to how to fix this? > > >> > > > > >> > >I already tried "pritugrade -Rr galeon". Lots of stuff was > > >> rebuilt, but both browsers still core dump :-( > > >> > > > > >> > > > > >> > > > > >> > > > > >> > did you build and install a new kernel? did you do mergemaster? > > >> > > >> Yes, and yes. > > >> > > >> Does that narow it down? > > > > > > > > > As a point of imformation, both mozilla and mozilla-devel > > > segv for me since I upgraded. Right now I'm still > > > using the linux version of netscape-4.8 so that I can > > > use the audio plugins. But the more I use mozilla-- > > > and galeon too, BTW--the more I like both. > > > > > > Anybody here subscribed to -ports and know if > > > things are broken?? > > mozilla and mozilla-devel are not broken. They work just fine. If you > see a segfault in these ports, it is most likely a font problem. It > could be other things, but since I have no other information to go on, I > will assume a font problem. To rule out fonts, you should try building > mozilla without Xft support. To do this, specify -DWITHOUT_XFT when > building mozilla. If the problem goes away, and you still want to use > Xft for anti-aliasing support, you can try to track down any bad fonts > you may have installed. Usually, that involves making sure you have the > XFree86 scalable fonts port installed, and you do _not_ have the > mozilla-fonts port installed. From there, you usually have to go font > by font, running fc-cache after each font removal, to track down the > offending font. My problem does not look like a font problem. Let me be specific. When I start Galeon, it comes up, and waits 4 or 5 seconds, then pops up a warning that the connection was refused by the home page (which is working for other clients at that time), when I close this popup. I get a crash of Galeon. This does not loook like a font problem to me. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030212024441.GA12824>