Re: How to fix a crashing Nautilus
On Tue, Jan 21, 2003 at 10:46:55PM -0500, Eloy A. Paris wrote:
> Ryan Verner <xfesty@computeraddictions.com.au> writes:
>
> > I had to get rid of ~/.nautilus, ~/.gnome2* and ~/.gconf* before I could run
> > nautilus successfully, guessing an earlier setting was clashing.
> >
> > nautilus seems really strange now - the tree on the left now has massive
> > 32x32 icons, and I can't seem to choose an icon theme (even with the icons
> > deb forementioned installed), the preferences doesn't seem to have an option
> > in it anymore to let me.
> >
> > gnome-panel keeps randomly freezing now too, and metacity window resizing
> > now seems to have this strange resize effect which gives the impression that
> > the system's lagging.
>
> I've noted this "system is lagging" feeling as well - one way I can
> easily see it is by right-clicking on the desktop: the context menu
> takes some time, about 1 second, to pop up, something that I had not
> experienced before. Another way is to move (by dragging) one icon on the
> desktop to another place in the desktop: there's a weird delay at the
> beginning of the operation.
>
> This is on a relatively fast machine, and with a fresh configuration (rm
> -Rf .gnome2* .nautilus .gconf*)
>
> I wonder what's causing all this "weirdness". Anyone else noticing this
> or other weird things?
I'm getting the same issues. granted I'm on an older computer. perhaps that
gives me a little perspective though. things are *much* slower for me than
they were a few days ago. I think it was either the upgrade to gtk 2.2 or
perhaps a metacity upgrade. when I drag around a box, it moves very slow, and
xfree86 starts using a large portion of my processor (60 - 70%, metacity at
around 10 - 15%, gnome-term (the app I'm moving around) at 10%, xterm (the
non-gtk app in the background, using a gtk app like nautilus or freecell
seemed to make things worse (around 10% or so)) at around 3%.
gtk apps seem to load much slower too. it seems like if galeon takes too long
to load, it'll crash. if I try to start it once, it'll usually crassh and I'll
have to try again. the second time it'll usually start, but not necessarily.
Sean
Reply to: