Red Hat Bugzilla – Bug 51043
GNOME leaves processes hanging around after exit
Last modified: 2007-04-18 12:35:31 EDT
Description of Problem: Exiting GNOME leaves two processes hanging around. How Reproducible: Always. Steps to Reproduce: 1. At the GDM login screen, log into GNOME 2. Log out 3. Log in at the console 4. Do "ps -x" Actual Results: "gconfd" and "oafd" are still running. Expected Results: "gconfd" and "oafd" were shut down with the rest of the GNOME processes upon GNOME exit. Additional Information:
There really is no reason for these processes to stop. GConf is a per application configuration registry that can be used by apps that are graphical or not. oafd allows CORBA enabled apps to find CORBA objects - again not a graphical or non-graphical item.
There is definite reason for these processes to stop. When a user is totally logged out, they should not consume resources. . Imagine a publicly accessible terminal in a lab - I'm sure you have lots of installations like this. Do you really want to waste two processes per user who has ever logged in to the GNOME desktop?!
Current rawhide gnome-core (well, I'm not sure it synced yet, but whatever I built on Friday or so) has a terrible hack to kill off oafd on logout, assuming you log out cleanly. If you ctrl-alt-backspace, you're on your own. gconfd will exit after 15 minutes if it is unused. If it doesn't exit then something is probably using it. I could change this time to 5 minutes, I'm not sure what would be best. If this contrasts with observed behavior, please reopen.
This defect is considered SHOULD-FIX for Fairfax.