On Tue, 2003-02-11 at 21:44, stan wrote: > 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.
Well, without a stacktrace or any logs, it's hard to make any other guess. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
