> > > > I know you've said previously that you have two instances of > > gnome-keyring-daemon running - is that still the case? Do you know when > > they are started? > > Immediately after logging in, but before running Evo, I have: > > 23795 /usr/bin/gnome-keyring-daemon --daemonize --login
That is what I get as well - presumably started by PAM. > > I run Evo, and get: > > 23795 /usr/bin/gnome-keyring-daemon --daemonize --login > 24608 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets > It is understandable why there are two processes, but the second one should have completed and gone away. Details on the command line options are at: http://live.gnome.org/GnomeKeyring/RunningDaemon To precis what it says, the --login option doesn't fully initialise the daemon, that is done by a separate process running with the --start option. What it looks like is that this second daemon can't find or talk to the initial --login daemon so takes over the role itself and so asks for the password to unlock the login keyring. I suppose one way to find out if that's true is to look at the files and sockets they are each using - the sockets are in /tmp/keyring-* - there should only be one directory owned by your username and containing 4 named sockets - you can also use lsof on the running processes to see what sockets they each have open. Which user owns each of the gnome-keyring-daemon processes? They should be owned by your username. There is also some mention of DBUS being used - is DBUS also started as part of your login process? P. _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
