Red Hat Bugzilla – Bug 59523
Last modified: 2008-05-01 11:38:01 EDT
Description of Problem:
The problem exhibits itself in nautilus, but I think I've traced it to fam.
Basically, after starting GNOME once the Nautilus desktop will come up.
Subsequent exits and restarts of GNOME often fail to start the Nautilus desktop.
Furthermore it is impossible to start the Nautilus file manager. In addition,
when this happens I am unable to use the GNOME logout feature--I must
CTRL-ALT-BACKSPACE. I've done some investigation and noticed that this only
seems to happen when fam is defunct in ps, i.e., ps -aex shows something like this
1237 ? Z 0:00 [fam <defunct>]
Issuing the command service xinetd restart seems to fix the problem, such that
when GNOME is restarted Nautilus does start as usual again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start GNOME, exit
2. start GNOME (did Nautilus start?; if so exit)
3. start GNOME (Nautilus almost surely will not have started by this point)
oh, this is hampton beta 1, just to be clear
I'm seeing this with every install I've done so far.
I think this might be a problem with xinetd, which may have poor support for RPC
services. I downgraded to xinetd from 7.2, and it seems to have fixed it.
Hmm. Haven't seen this yet on my system, but it I wouldn't be supprised at all
if xinetd is the culprit. The support for wait rpc services is not widely used,
and has caused trouble before.
I'm cc:ing trond on this, since he owns xinetd.
This is actually a xinetd problem. It fails to reap the fam child if there are
no other services that xinetd handles.
Created attachment 52244 [details]
Patch for xinetd that solves the problem
*** Bug 62515 has been marked as a duplicate of this bug. ***
*** Bug 62289 has been marked as a duplicate of this bug. ***
Moving over should-fix status from dup.
I can report success with this problem when using xinetd-2.3.4-0.8 from rawhide
This is still occuring in skipjack beta2. It would be helpful if there was an
up2date channel for skipjack-beta2 and this fix was available.
Another note -- the problem goes away after reboot but appears again after