Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On Sun, 2021-12-19 at 11:14 -0500, George Reeke wrote: > On Sun, 2021-12-19 at 15:17 +, Pete Biggs wrote: > > > > 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. I > > > Pete, thanks for the info. Yes, for me those passwords are the same. > So what is PAM and where can I read about how to configure it? $ man pam poc ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
Thank you, Pete. Seahorse works fine. Dbus is installed and running. I was just trying to figure out whether it is running correctly using dbus-monitor to compare signals when Chrome vs. Evolution are started with a locked keyring. (Don't know what I'm doing here; just guessing.) And the first time I ran Evolution with dbus-monitor active, I actually got the password prompt; i.e., it is now working correctly. I have no idea what changed (or what I did) to make it work, but at least for the moment all is well. Will get back to it if it starts acting up again. Thank you all for your help. On Sun, Dec 19, 2021, at 11:18 AM, Pete Biggs wrote: > On Sun, 2021-12-19 at 10:43 -0500, Julius Merphik via evolution-list > wrote: > > Thanks, Pete and others. I do know the different between seahorse and > > gnome-keyring. > > Possibly, but others seemed to be getting them confused. > > > > > 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. > > What about seahorse? Does that work OK? (To see if it is a difference > between gnome vs non-gnome application.) > > > > > Again, I conclude that the issue is with Evolution. Is my reasoning > > faulty? > > It's possible that chrome uses a different mechanism for accessing the > gnome-keyring. Is DBus functioning correctly on your system? > > The bottom line is that I, and many, many others, have been using > evolution with gnome-keyring without any problems for many years and > versions. If there was an issue with evolution and passwords there > would be a lot more noise about it as it's a fundamental feature. The > conclusion then is that the issue is with your setup and not with > evolution. > > > 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
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
Thank you, Ralf. I did see that. The solution sounds ideal. Lots of info in those links, but no step-by-step guide for Ubuntu 20.04. And unfortunately I don't know enough to be able to implement it without a step-by-step guide. :-( On Sun, Dec 19, 2021, at 11:15 AM, Ralf Mardorf via evolution-list wrote: > On Sun, 19 Dec 2021 10:43:00 -0500, Julius Merphik wrote: > >Is my reasoning faulty? > > Did you read the link I posted? > > On Sun, 19 Dec 2021 08:38:33 -0500, Julius Merphik wrote: > >As an aside, the commonly mooted solution to the larger issue is to > >set a blank keyring password. This would be preferable to me, as it is > >a single-user machine with a fully encrypted hard drive. > > "Alternatively, if using GDM and LUKS, GDM can unlock your keyring if > it matches your LUKS password. For this to work, you need to use the > systemd init in your mkinitcpio.conf as well as the appropriate kernel > parameters. See [1] for more details". - > https://wiki.archlinux.org/title/GNOME/Keyring#PAM_step > ___ > 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
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On Sun, 19 Dec 2021 16:18:04 +, Pete Biggs wrote: >The bottom line is that I, and many, many others, have been using >evolution with gnome-keyring without any problems for many years and >versions. But not necessarily with an encrypted hard drive ;). My drive isn't encrypted, the OP's drive is "fully encrypted". ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On Sun, 2021-12-19 at 10:43 -0500, Julius Merphik via evolution-list wrote: > Thanks, Pete and others. I do know the different between seahorse and > gnome-keyring. Possibly, but others seemed to be getting them confused. > > 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. What about seahorse? Does that work OK? (To see if it is a difference between gnome vs non-gnome application.) > > Again, I conclude that the issue is with Evolution. Is my reasoning > faulty? It's possible that chrome uses a different mechanism for accessing the gnome-keyring. Is DBus functioning correctly on your system? The bottom line is that I, and many, many others, have been using evolution with gnome-keyring without any problems for many years and versions. If there was an issue with evolution and passwords there would be a lot more noise about it as it's a fundamental feature. The conclusion then is that the issue is with your setup and not with evolution. 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
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On Sun, 19 Dec 2021 10:43:00 -0500, Julius Merphik wrote: >Is my reasoning faulty? Did you read the link I posted? On Sun, 19 Dec 2021 08:38:33 -0500, Julius Merphik wrote: >As an aside, the commonly mooted solution to the larger issue is to >set a blank keyring password. This would be preferable to me, as it is >a single-user machine with a fully encrypted hard drive. "Alternatively, if using GDM and LUKS, GDM can unlock your keyring if it matches your LUKS password. For this to work, you need to use the systemd init in your mkinitcpio.conf as well as the appropriate kernel parameters. See [1] for more details". - https://wiki.archlinux.org/title/GNOME/Keyring#PAM_step ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On Sun, 2021-12-19 at 15:17 +, Pete Biggs wrote: > > 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. I > Pete, thanks for the info. Yes, for me those passwords are the same. So what is PAM and where can I read about how to configure it? George ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
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
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
> > 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
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
PS: On Sun, 19 Dec 2021 07:11:41 +0100, I wrote: >if I log in by lightdm after startup, then start Evolution and right >after that retrieve emails, I have nothing to do. And I'm never asked to enter a password. >If I wait for a while before retrieving emails, a small window opens, >asking for the password. Just one time and then never again. ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
Hi, this is how it is set up on my machine. [rocketmouse@archlinux ~]$ pacman -Q gnome-keyring gnome-keyring 1:40.0-1 [rocketmouse@archlinux ~]$ cat /etc/pam.d/* | grep gnome auth optional pam_gnome_keyring.so #auth optional pam_gnome_keyring.so -auth optionalpam_gnome_keyring.so -sessionoptionalpam_gnome_keyring.so auto_start -auth optionalpam_gnome_keyring.so -sessionoptionalpam_gnome_keyring.so auto_start [rocketmouse@archlinux ~]$ ps aux | grep -ekeyring -eseahorse | grep -v grep rocketm+ 12368 0.0 0.0 385572 9556 ?SLl 02:48 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets I don't know if this Wiki is helpful: https://wiki.archlinux.org/title/GNOME/Keyring#PAM_step Remember, this is what's happening on my machine: On Sun, 19 Dec 2021 07:11:41 +0100, I wrote: >if I log in by lightdm after startup, then start Evolution and right >after that retrieve emails, I have nothing to do. If I wait for a while >before retrieving emails, a small window opens, asking for the >password. Regards, Ralf ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
Thanks for replies, everyone. I use auto-login on Ubuntu; hence the keyring is not automatically opened when I login. If, after logging in but before unlocking the keyring, I: => Start Chrome: I get a prompt to enter the keyring password. Then start Evolution: All is well. => Start Evolution: I *do not* get a prompt to enter the keyring password; it just hangs. Then start Chrome: It hangs too. Since I get a keyring prompt with Chrome, but not with Evolution, I concluded that the issue is with Evolution. That said, I don't know how it all works on the backend, so that's just a guess. Is there a way of tracing the calls between Chrome/Evolution and the keyring, so that I can see what is going on on the backend? That might help see what (if anything) Chrome and Evolution are doing differently, and thus help isolate the issue. (P.S. As an aside, the commonly mooted solution to the larger issue is to set a blank keyring password. This would be preferable to me, as it is a single-user machine with a fully encrypted hard drive. However, I have tried this many times, and it does not "stick"; i.e., after a few days or weeks the keyring, as if by magic, reacquires its password and I am back where I started. So I gave up on this.) On Sun, Dec 19, 2021, at 1:11 AM, Ralf Mardorf via evolution-list wrote: > On Sat, 2021-12-18 at 21:54 -0500, George Reeke wrote: > > On Sun, 2021-12-19 at 01:42 +0100, Ángel wrote: > > > Evolution asks the Keyring, and if it isn't there it would show the > > > password prompt (i.e. it it was working). > > > Note that if the keyring wasn't running it should be activated > > > automatically. > > > > 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. [snip] > > Hi, > > if I log in by lightdm after startup, then start Evolution and right > after that retrieve emails, I have nothing to do. If I wait for a while > before retrieving emails, a small window opens, asking for the password. > > $ lsb_release -d; pacman -Q evolution lightdm openbox seahorse > Description: Arch Linux > evolution 3.42.2-1 > lightdm 1:1.30.0-4 > openbox 3.6.1-8 > seahorse 1:41.0-2 > > Regards, > Ralf > ___ > 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
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On Sat, 2021-12-18 at 21:54 -0500, George Reeke wrote: > On Sun, 2021-12-19 at 01:42 +0100, Ángel wrote: > > Evolution asks the Keyring, and if it isn't there it would show the > > password prompt (i.e. it it was working). > > Note that if the keyring wasn't running it should be activated > > automatically. > > 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. [snip] Hi, if I log in by lightdm after startup, then start Evolution and right after that retrieve emails, I have nothing to do. If I wait for a while before retrieving emails, a small window opens, asking for the password. $ lsb_release -d; pacman -Q evolution lightdm openbox seahorse Description:Arch Linux evolution 3.42.2-1 lightdm 1:1.30.0-4 openbox 3.6.1-8 seahorse 1:41.0-2 Regards, Ralf ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On Sun, 2021-12-19 at 01:42 +0100, Ángel wrote: > Evolution asks the Keyring, and if it isn't there it would show the > password prompt (i.e. it it was working). > Note that if the keyring wasn't running it should be activated > automatically. 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. 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. 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. Best to all, George Reeke ___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution hangs if Gnome Keyring isn't open before starting
On 2021-12-18 at 09:20 -0500, Julius Merphik wrote: > Using Evolution 3.36.5-0ubuntu1 on Ubuntu 20.04.3, Evolution hangs if > the Gnome Keyring isn't already open when Evolution is started, at > least when Evolution is configured to access more than one Google > account. Hello Julius Are you using the Gnome Desktop Environment or another DE? If you are using GNOME, isn't gnome-keyring already autostarted by it? > Expected behavior: If Gnome Keyring isn't open when Evolution is > started, a password prompt is displayed to unlock the keyring. Evolution asks the Keyring, and if it isn't there it would show the password prompt (i.e. it it was working). Note that if the keyring wasn't running it should be activated automatically. > Actual behavior: For e-mail, folders are never loaded, each account > says "Loading...," and eventually this error message appears: "Failed > to connect account '[account name]'. The reported error was 'Failed > to authenticate: Timeout was reached'." Calendars do not sync. > Evolution hangs, and has to be force-closed or killed from the > command line. It seems that the keyring hangs without providing any answer. This causes evolution to stall awaiting, until it finally reaches a timeout. > In addition, this causes other applications that rely on the Gnome > Keyring (e.g., Chrome) to fail to start until Ubuntu has been > restarted. Since Chrome is failing as well, this doesn't seem a problem of evolution. It seems implicit in how you phrased it, but can you confirm that if you *manually* launch gnome-keyring before running evolution it does work? Thus I think the problem may actually be somethign on the lines of "when gnome-keyring is launched by evolution it fails to load and freezes". > Suggestions for fixing or reporting this as a bug much appreciated. > Thank you. Both evolution and gnome-keyring bug trackers are at https://gitlab.gnome.org/GNOME The part I find more interesting is that chromium fails as well, but gnome-keyring working if it was already opened. If evolution request contained something that made it hang, I would expect it to always fail. I *suspect* that if, after one failed opening of evolution, you killed gnome-keyring, then you would be able to open chromium without having to resort to a full system restart. As a way of debugging, you could watch the dbus messages, trying to make sense on when it fails. I don't expect them to be too readable, though. Best regards ___ 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] Evolution hangs if Gnome Keyring isn't open before starting
Using Evolution 3.36.5-0ubuntu1 on Ubuntu 20.04.3, Evolution hangs if the Gnome Keyring isn't already open when Evolution is started, at least when Evolution is configured to access more than one Google account. Expected behavior: If Gnome Keyring isn't open when Evolution is started, a password prompt is displayed to unlock the keyring. Actual behavior: For e-mail, folders are never loaded, each account says "Loading...," and eventually this error message appears: "Failed to connect account '[account name]'. The reported error was 'Failed to authenticate: Timeout was reached'." Calendars do not sync. Evolution hangs, and has to be force-closed or killed from the command line. In addition, this causes other applications that rely on the Gnome Keyring (e.g., Chrome) to fail to start until Ubuntu has been restarted. Suggestions for fixing or reporting this as a bug much appreciated. Thank you.___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
