Re: How to fix a crashing Nautilus

[Johannes Rohr <j.rohr@comlink.apc.org>]

Christian Marillat <marillat.christian@wanadoo.fr> writes:

> Xavier Bestel <xavier.bestel@free.fr> writes:
> 
> > Le mer 22/01/2003 à 14:06, Christian Marillat a écrit :
> 
> [...]
> 
> > I tried them, but gnome-theme-manager hangs before showing a window:
> 
> > Program received signal SIGINT, Interrupt.
> > [Switching to Thread 16384 (LWP 29106)]
> > 0x409f5934 in write () from /lib/libc.so.6
> > (gdb) whe
> > #0  0x409f5934 in write () from /lib/libc.so.6
> > #1  0x40458b50 in __JCR_LIST__ () from /lib/libpthread.so.0
> > #2  0x40d30a58 in Client::writeToServer(char*, int) () from /usr/lib/libfam.so.0
> 
> Seem to be a fam problem. Try to logout/login or kill/restart fam.

So what? After doing what you suggest, famd is spawned again and the
whole thing repeats itself. (fully reproducible for me under any
account).

Only fully disabling famd makes the theme manager work. The same goes
for gnome-keybinding-properties.

bugzilla.gnome.org is *full* of related reports. Upstream has to fix
it.

Thanks,

Johannes
-- 
~/.signature under construction