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
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
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
[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
Re: [Evolution] Adding Google account broke Evolution
Thanks, everyone. I'm going to work on this again over the weekend, when it will be less of a problem if I break something again. FTR, my personal Google account has 2FA and I am using CalDAV with an app password to login. That works. My work Google account does not seem to offer 2FA, so I was using CalDAV with the Google setting "allow insecure apps." Will evaluate the alternatives and test over the weekend. On Fri, Dec 17, 2021, at 2:16 AM, Milan Crha via evolution-list wrote: > On Thu, 2021-12-16 at 11:05 -0800, Alex Doll wrote: > > I didn't pursue a fix, I just removed my google accounts from > > Evolution and disabled the Google account from the Gnome panel to > > make the login prompts go away. > > > Hi, > you should be able to use the OAuth2, especially with the 3.42.2, which > you seem to be using. It can be a bit more problematic with the ancient > 3.36.5, though I think not so hard too. > > I do not think there are any easier ways how to make it work than what > Evolution offers (there had have some glitches in the process before > 3.40 or some such version), just do Edit->Accounts->Add->Collection > Account->[fill a @gmail.com address]->Lookup->(finds 8 candidates > here)->Next->Next->Next->..., then fill in OAuth2 credentials and > that's all. > > Alternatively, File->New->Mail Account->[fill a @gmail.com address] > ->Next->Next->Apply. Then you are asked for the OAuth2 credentials and > that's all. > > You get all your mail, tasks, contacts (CardDAV) and (enabled for sync) > calendars (CalDAV). There are shown related links in the account > wizards. > > The third option is to add a Google account in the GNOME Online > Accounts, which the evolution-data-server talks to and provides the > information for Evolution (and any other application using the > evolution-data-server). > > Bye, > Milan > > ___ > 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
[Evolution] Adding Google account broke Evolution
Evolution was working perfectly with one local e-mail, one remote e-mail (IMAP), and two remote calendars (one CalDAV + one Google Calendar via CalDAV, using an app password). Evolution v. 3.36.5-0ubuntu1 on Ubuntu 20.04.3. This morning I added my Google work calendar and Gmail work e-mail (IMAP); no 2FA available on this account, so I enabled less secure app access in Google. Everything appeared to be working fine, so I shut down my computer. The next time I started it, I was unable to access *ANY* of my non-local e-mail or calendar accounts. In the e-mail pane, both accounts just said "Loading..." with the spinning circle. They were never able to connect or display the folder list or any messages. Re calendars, when I started Evolution, it displayed the following error message for each non-local calendar: "Failed to connect calendar 'CalDAV: [account]' / Unauthorized." Pressing "Reconnect" did nothing; or, in the case of my Google work account, it displayed what appeared to be a Google popup asking for my username and password, and then asking me to confirm that I wanted to allow Evolution to access my account. When I clicked yes, it displayed an Evolution popup saysing "Google Calendar authentication request / Login to your Google account and accept conditions in order to access your calendar 'Google: [employer name]'. / URL: none-local:// / Requesting access token, please wait..." Then it stalled there. After deleting my Google work account (email and calendar) from Evolution, I was able to reactivate my Fastmail email account by deleting and reinstalling it, but I could not get any non-local calendars working again. In the end, I deleted all Evolution data and config files, deleted all email and calendar login credentials from the keyring, uninstalled and purged Evolution, then reinstalled and rebuilt everything from scratch. Now I am back to where I started. My question is: Does anyone have any thoughts about what might have caused this, and how I can avoid it? I need to have my work account accessible, but I really, really don't want to go through that again. Many thanks, Julius___ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
