GNOME Bugzilla – Bug 607085
Multiple instances of gnome-keyring-daemon since upgrading gnome from 2.28.0 to 2.29.5
Last modified: 2010-02-17 15:22:41 UTC
The summary says it all. I just finished rebuilding gnome using this week's 2.29.5 releases. I notice 3 instances of gnome-keyring-daemon running instead of the single instance I had in 2.28. Don't know if this is a bug, but as several other apps have developed problems (hangs), I though I would report it in case this was some sort of keyring deadlock.
Is this still an issue? This sounds like an issue that may have been fixed recently, but I'm not sure. If so could you give the complete ps output for those processes? I'm interested in the arguments to each process. Thanks!
Here they are: ronis 2967 0.0 0.1 32000 2220 tty1 Sl 12:30 0:00 gnome-keyring-daemon --start --components=ssh ronis 2970 0.0 0.1 23808 2328 tty1 Sl 12:30 0:00 gnome-keyring-daemon --start --components=secrets ronis 2973 0.0 0.1 23808 2304 tty1 Sl 12:30 0:00 gnome-keyring-daemon --start --components=pkcs11
I just upgraded to 2.29.90; the problem remains.
Yes, I figured out what the problem is. It's a scenario where the user is running without the PAM module. I'll work on fixing it, but didn't get a chance to do so before 2.29.90
Fixed in git master. If you can, could you try rebuilding from git, and see if this fixes your problem? commit 43590189620c9dc5cda9854fef899fe89b24d308 Author: Stef Walter <stef@memberwebs.com> Date: Sun Feb 14 05:15:10 2010 +0000 [daemon] Rework the startup again, singleton crontrolled via dbus. Account for starting dbus via the autostart files (ie: various components individually), but without a gnome-keyring-daemon running from pam. This previously caused multiple processes. We use a dbus singleton in this case.
I just tried building the git-master. Configure dies with: configure.in:336: warning: macro `AM_PATH_LIBGCRYPT' not found in library Running autoconf... configure.in:336: error: possibly undefined macro: AM_PATH_LIBGCRYPT If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. make: *** [pre-configure] Error 1 I had libgcrypt-1.4.0 installed, and just upgraded to 1.4.5 (the current release). The problem remains.
Have you installefd the -dev or -devel package of libgcrypt in order to compile software that depends on it? Let's leave this marked as fixed, unless you actually find a real problem with the fix.
OK I think that slackware and/or the manual build of libgcrypt installs the devel packages, at least /usr/share/aclocal/libgcrypt.m4 /usr/include/gcrypt.h /usr/include/gcript-module.h /usr/lib/libgcrypt.so are all present. In any event, I was able to build gnome-keyring-2.29.5 with no problems. On thing different with the git build is that autogen.sh is run first, whereas I used the included configure that came with the released tarballs.
OK, the problem seems to be my aclocal not looking in the right places. I fixed this by setting up some links. gnome-keyring now builds and only one main instance is run when I start (here are two children threads though). Thanks for your help.
Great! Thanks for catching this problem.