I don't think that's it. Because see, when I reboot fresh after say
going into Windows, and go into Gnome, it says sawfish isn't compliant and
runs really slow.
Once I open Netscape (which is about 10-15 minutes after it's been running
bad and having all these weird errors and quirks), it core dumps and causes
X to crash.
THEN when I open X, it's juuuuust fine. No quirks, no slowdowns.
ps aux has no Netscape or Communicator or anything in it unless Netscape is
actually running (which it can only do for about 5 seconds maximum).
----- Original Message -----
From: "Michael J. Ruhl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 29, 2000 11:09 AM
Subject: Re: Gnome compliance?
> I have had netscape processes take up 80% of my CPU, even after it
> appeared that the browser was gone.
>
> After netscape dies, do a top command or ps -aux and see if there is
> any netscape "helper" processes hanging out. That might be your
> problem.
>
> Good luck,
>
> Mike
>
> Dolgan wrote:
> >
> > >
> >
> > More information.
> >
> > It seems that whenever Netscape crashes (every time I use it), and then
when
> > I do ctrl-alt-backspace to kill X (if I kill Netscape, then it kills X
and
> > renders it unrestartable until next reboot - no idea why), it core dumps
etc
> > etc.
> >
> > But here's the killer. When I go back into X after that, Gnome works
fine.
> > Netscape still doesn't. But Gnome works fine. So does sawfish.
> >
> > Here I say, W T F ?
> >
> > What IS this? Something to do with Netscape, X, and Sawfish...
> >
> > I wish I wasn't so inexperienced. Any help on this greatly appreciated.
> >
> > The problem, once again, is that Gnome is really slow and doesn't think
> > sawfish is wm-compliant until Netscape core dumps.
> >
> > >
> > >
> > > Dolgan had the audacity to say:
> > > > OK, this problem got a whole lot weirder, but a whole lot
brighter.
> > > >
> > > > I noticed that Netscape kept crashing whenever I went to a site (It
> > > > still does - but there's always
> > > > Mozilla and right now, I want GNOME working. One problem at a time,
> > > > right?), so I installed
> > > > Netscape 3 for experiment's sake.
> > > >
> > > > Suddenly, I restarted X, and sawfish was "gnome compliant" and Gnome
was
> > > > zippy. That makes me
> > > > think that sawfish's compliancy is causing Gnome to be sluggish -
> > > > somehow.
> > > >
> > > > Unfortunately, next time I restarted X it went back to crap.
> > > >
> > > > Does anyone know what could be related to SAWFISH that could be
causing
> > > > Gnome to not think it's
> > > > wm-compliant?
> > > >
> > > >
> > > > On Wed, 28 Jun 2000, Dolgan wrote:
> > > > ...
> > > > : I installed clean from a 6-27-2000 snapshot. That was yesterday.
> > > > Wouldn't
> > > > : that make the ports updated, or not..?
> > > >
> > > > Hmm, it should yes.
> > > >
> > > > : Why would it be a ports thing, though? It's Gnome 1.2.1... latest.
Is
> > > > there
> > > > : something weird with ports?
> > > > : Latest sawfish too.
> > > >
> > > > Yeah, but ports often apply several patches to make things work
right on
> > > >
> > > > FreeBSD, those patches could have been updated without a version
upgrade
> > > >
> > > > of gnome. Given that you installed from a snapshot of yesterday, you
> > > > should have the latest ports though. At this point, I'm not sure
what
> > > > the
> > > > problem is.. Maybe someone who runs the combination would have an
idea.
> > > >
> > > > * Matt Heckaman - mailto:[EMAIL PROTECTED]
http://www.lucida.qc.ca/ *
> > > >
> > > > --
> > > > Dolgan
> > > > icq@14444322
> > > > [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > > with "unsubscribe freebsd-stable" in the body of the message
> > > >
> > >
> > > --
> > > Coleman Kane
> > > President,
> > > UC Free O.S. Users Group - http://pohl.ececs.uc.edu
> >
> > --
> > Dolgan
> > icq@14444322
> > [EMAIL PROTECTED]
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
