Bug 231139 - [PATCH] gconfd-2 daemon never exits (after all user applications quit)
[PATCH] gconfd-2 daemon never exits (after all user applications quit)
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: GConf2 (Show other bugs)
4.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
http://bugzilla.gnome.org/show_bug.cg...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-06 09:28 EST by wingc
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2007-0764
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-15 11:06:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
[PATCH] ensure that gconfd shuts down after all clients exit (from GNOME CVS) (498 bytes, patch)
2007-03-06 09:28 EST, wingc
no flags Details | Diff

  None (edit)
Description wingc 2007-03-06 09:28:29 EST
Description of problem:

The 'gconfd-2' daemon, which is started up by applications that use GConf, never
exits after all GConf applications quit.  This bug was fixed in gconf-2.10.1.  I
have attached the patch from the GNOME source repository, which applies fine to
the version of GConf in RHEL4 (2.8.1) and I confirmed it fixes the problem.

This is mainly annoying on public access Unix systems with a large number of
users, because over time these gconf processes will pile up.

Version-Release number of selected component (if applicable):

The bug is present in the GConf2 RPM from RHEL4 (GConf2-2.8.1-1)

How reproducible:

always

Steps to Reproduce:
1. log into a machine (remotely) and run a program that uses GConf, e.g. 'gedit'
2. note that the program has spawned a 'gconfd-2' process in the background
3. quit the GConf-using program
  
Actual results:

The gconfd-2 process does not exit, but stays around forever.  (You can also
observe this effect by starting an X session with GNOME; after logout, a
'gconfd-2' process will hang around)

Expected results:

The gconfd-2 process should exit within 30 seconds of the time that the last
GConf client program has exited.

Additional info:

This bug was fixed in GNOME sources by a commit on 2005-06-13, labeled:

2005-06-13  Mark McLoughlin  <mark@skynet.ie>

	Fixes bug #306937 - gconfd-2 not shutting down when its
	no longer in use.

	* gconf/gconfd.c: (no_databases_in_use): account for the
	fact that the default database is on the global list of
	databases now too.


Currently, this change is revision 1982 to gconf/gconfd.c in the GNOME
Subversion repository for 'gconf'.


The original Bugzilla entry in GNOME CVS is here, which also contains a link to
the patch:

http://bugzilla.gnome.org/show_bug.cgi?id=306937


The patch applies fine to the version of GConf2 in RHEL4 (GConf2-2.8.1-1) and
fixes the problem there as well.  I rebuilt the GConf2 RPM including the patch
and the gconfd-2 daemon now exits correctly.
Comment 1 wingc 2007-03-06 09:28:29 EST
Created attachment 149337 [details]
[PATCH] ensure that gconfd shuts down after all clients exit (from GNOME CVS)
Comment 2 Ray Strode [halfline] 2007-03-06 10:19:15 EST
Adding to rhel 4.6 proposed list.
Comment 3 RHEL Product and Program Management 2007-05-09 01:56:37 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 4 Ray Strode [halfline] 2007-07-24 11:42:26 EDT
devel ack for 4.6
Comment 5 Ray Strode [halfline] 2007-07-24 17:03:23 EDT
marking MODIFIED for QA, patch building into GConf2-2.8.1-1.el4 
Comment 9 errata-xmlrpc 2007-11-15 11:06:51 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2007-0764.html

Note You need to log in before you can comment on or make changes to this bug.