On Fri, 12 Jul 2002 11:22:26 +0200, Jim Sproull wrote: > On Fri, 2002-07-12 at 08:35, Frederic Crozat wrote: >> On Fri, 12 Jul 2002 10:28:32 +0200, Jim Sproull wrote: >> >> > On Fri, 2002-07-12 at 07:57, Frederic Crozat wrote: >> > On Fri, 12 Jul 2002 09:53:02 +0200, Jim Sproull wrote: >> > >> > > I keep getting seg faults when starting this release of nautilus. I >> > > upgraded from 2.0.0-7 to -8, which also seg faulted at start up. -9 has >> > > similar behaviour. I tried uninstalling "*nautilus*", and reinstalling >> > > -9 with similar results. Has anyone else experienced this behaviour? >> > > Is there a way I can track down where it's dying on my system? >> > >> > Which assertion are you getting ? >> > >> > Check that both /var/lib/gnome/desktop and ~/.gnome-desktop exists.. >> > (~/.gnome-desktop should be created by nautilus anyway..) >> > >> > And please, stop posting in HTML... >> > >> > -- >> > Frédéric Crozat >> > MandrakeSoft >> > >> > >> > >> > Both /var/lib/gnome/desktop and ~/.gnome-desktop do exist >(/var/lib/gnome/desktop/ is empty). I tried rm >> > -rf ~/.gnome-desktop to see if it was something there causing the >> > problems, but that didn't resolve the error. >> > >> > I'm not seeing any error messages at all on the console, but here is the >> > debugging information generated by gnome's bug handler: (is there a >> > more useful error log stored somewhere?) >> >> Are you sure there is nothing in ~/.xsession-errors ? >> >> Stack trace isn't useful since we don't ship packages with debug info.. >> >> What do you have in ~/.nautilus ? >> >> Could you try moving it away to see if it fixes the problem ? >> -- >> Frédéric Crozat >> MandrakeSoft >> > > > I removed ~/.nautiluls and ~/.gnome-desktop (again, just to be safe) > and am still getting the seg fault. I did a > > tail -f ~/.xsession-errors > > while starting nautilus and nothing showed up. > To double check, I created a brand new user, logged in, started X from > the command line (no window manager), then started nautilus. > I still got the seg fault. And no error messages on the command line. > Could there be a dependancy not satisfied? (rpmdrake doesn't report any)
Maybe.. Check that fam is running correctly : rpcinfo -p should have the following line.. 391002 2 tcp 32769 sgi_fam Could you try by creating a new user to see if it crashes ? -- Frédéric Crozat MandrakeSoft
