*** This bug has been marked as a duplicate of 2586 ***
This bug report tells me absolutely nothing of value. fam daemon running, or started? how do you know its not working? what tests? what error messages? what does "ps aux |grep [f]am - " tell you?
I got this reply by email: >fam daemon running, or started? how do you know its not working? what >tests? A nautilus view in the home dir A shell in the home dir touch ~/ff ls shows ~/ff nautilus doesn't show it, (mandrake has no trouble with this test) >what error messages? None >what does "ps aux |grep [f]am - " tell you? root 3797 0.0 0.2 2564 1176 ? S Jul28 0:00 /usr/bin/fam -T 0 -- Groeten, Marc Geerlings
More comments (note that I'm not a fam expert and this is not my bug :) okay, with my setup the same tests work: spider@Darkmere tmp.images $ ps aux |grep [f]am spider 4601 0.0 0.2 2640 800 ? S Jul26 0:00 /usr/bin/fam -T 0 touch, ls, rm and it instantly shows up in nautilus nautilus-2.0.2 fam-oss-2.6.7-r1
Well i got fam running, but nautilus won't update either. I noticed it earlier on, just never think of making a bugreport for something like that :)
If this is any help (only "error" I can find while compiling fam-oss on 1.4 with GCC3.2-r1): * Working directory: /var/tmp/portage/fam-oss-2.6.7-r1/work/fam-2.6.7... * Cannot apply any patch, running libtoolize... Using `AC_PROG_RANLIB' is rendered obsolete by `AC_PROG_LIBTOOL' You should update your `aclocal.m4' by running aclocal. That sounds disturbing to me, may be nothing though. And yes I also have this bug happening to me, very annoying.
I emerged the new masked gnome stuff (which includes a new nautilus, ver 2.0.6) and FAM began to work again. Should mean the error isn't in the fam ebuild.
My experience with fam is that it doesn't work too well unless you add it to your default runlevel. Trying to start it manually doesn't resolve the problem, but like I said, once you add fam to the default runlevel, everything should be just fine. Closing.
