Thanks, Pete and others. I do know the different between seahorse and gnome-keyring. But maybe I'm not explaining this well:
1. As I said, I use Ubuntu auto-login, so the keyring is *not* unlocked at login. The keyring process is, however, started as follows: ~$ ps -fe | grep keyring [username] 946 1 0 10:34 ? 00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login 2. When I start Evolution with the keyring locked, I am *not* prompted to enter my keyring password, and Evolution hangs. By contrast, when I start Chrome with the keyring locked, I am prompted to enter my keyring password. Again, I conclude that the issue is with Evolution. Is my reasoning faulty? On Sun, Dec 19, 2021, at 10:17 AM, Pete Biggs wrote: > > > > I can confirm that I have seen the same problem for a long time > > with my older CentOS-7-supplied Evolution 3.28.5 under Mate. > > I can add that when I log in after a bootup, Seahorse is not running. > > If I start evolution first, it asks for the password. If instead of > > entering it, I then start seahorse with my login password, evolution > > gets the email password from seahorse and I don't have to answer its > > query. If I start seahorse first, evolution never asks me for a > > password. > > I think it's important to get the terminology and function of the > various programs correct so that there's no confusion. > > Seahorse is the Gnome frontend for managing passwords, encryption keys > and so on. It does not store any information itself, it's just a > frontend. > > gnome-keyring is the backend daemon that stores passwords and keys (and > other things). Various applications use gnome-keyring to securely > store information - evolution is one of those. (Well, technically, > evolution uses libsecret that in turn uses the DBus Secret Service API > that allows any backend store, but gnome-keyring is currently the only > one that provides it.) > > > > > My conclusion is that this is not an evolution problem at all, > > but a problem with getting seahorse, or whatever machinery is > > behind it, or whatever it is you call Keyring, to start at login. > > Running seahorse will start gnome-keyring if it isn't already present. > It is the presence of gnome-keyring that is important, not the presence > of seahorse. > > > I have been unable to find a seahorse discussion group to bring > > this up. It might have to do with Mate vs. gnome in my case, > > but the similarity of my problem to the one posted suggests it is > > not that, but some machinery that is common to gnome and Mate > > startup independent of evolution. Further insight would be welcome. > > Gnome login will automatically start gnome-keyring and unlock the > default/login keyring. You can do the same thing for other desktop > environments by setting up PAM correctly. Note this only works if the > login password is same as the default keyring password. If the > passwords are different or the login password is not available (i.e. if > you start it outside the login process) then you will be prompted for > the password. > > P. > > > _______________________________________________ > evolution-list mailing list > evolution-list@gnome.org > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list >
_______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
