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 384781 - Gconf not working properly after daemonize
Gconf not working properly after daemonize
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: Daemon
git master
Other Linux
: Normal normal
: 1.0.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks: 443561
 
 
Reported: 2006-12-11 18:12 UTC by Stef Walter
Modified: 2011-03-09 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stef Walter 2006-12-11 18:12:03 UTC 
In the various daemons gconf doesn't work properly after the daemon has been forked. Either reading settings don't work, or notifications of changed settings don't work.
Comment 1 Stef Walter 2006-12-11 18:14:50 UTC 
This is a tough one, but I've committed the first set of fixes. This seems to fix the daemons read gconf keys. However notifications don't seem to be working yet.

2006-12-11  Nate Nielsen  <nielsen@memberwebs.com>

    * agent/seahorse-agent-main.c:
    * daemon/seahorse-daemon.c:
    * libseahorse/seahorse-gconf.c:
    * libseahorse/seahorse-gconf.h: Fix reading of gconf keys for daemons
    after forking. See bug #384781
Comment 2 Adam Schreiber 2007-06-03 17:36:14 UTC 
This bug blocks bug 443561.
Comment 3 Stef Walter 2011-03-09 16:09:56 UTC 
We no longer use notifications in the daemon, so closing. Additionally seahorse-daemon probably won't be around much longer, once libcryptui functionality is merged into libgcr.