After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 97651 - Gconfd continues to run after logging out -- causes umount to fail
Gconfd continues to run after logging out -- causes umount to fail
Status: RESOLVED DUPLICATE of bug 97361
Product: GConf
Classification: Deprecated
Component: gconf
1.2.x
Other other
: Normal major
: ---
Assigned To: GConf Maintainers
GConf Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-11-04 17:41 UTC by W. Michael Petullo
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description W. Michael Petullo 2002-11-04 17:41:05 UTC
The gconfd-2 daemon is run by many GNOME applications to manage
configurations.  Gconfd-2 remains running for some time after the
application which used it quits.  This allows other applications to use
gconfd-2 without having to start and stop the daemon too much.  This is a
good idea.

The problem comes when a system tries to unmount a user's home directory
when the user logs out.  For example, pam_mount unmounts an encrypted home
directory when I log out of my system.

Gconfd-2 continues to run even when a user logs out.  This causes the
unmounting of the user's home directory to fail because gconfd-2 keeps the
following files open:

/home/user/.gconfd/lock/<random string>
/home/user/.gconf/%gconf-xml-backend.lock/<random string>
/home/user/.gconfd/saved_state

Gconfd-2 should exit or close the above files when a user logs out.
Comment 1 Havoc Pennington 2003-03-06 04:50:46 UTC

*** This bug has been marked as a duplicate of 97361 ***