Description of problem: ======================= Access to gmail from this version of evolution does seem very much erratic. With evolution From gnome 3.14 (fc21) it still work correctly. Version-Release number of selected component (if applicable): ============================================================= evolution-3.16.2.1-2.fc22 How reproducible: ================= Very frequently but not consystently. Steps to Reproduce: 1. Connect to a google account 2. Enable both mail and calendar Actual results: =============== Mail mostly works, but sometimes error messages appear. Calendar does not work at all. Error messages appear. Expected results: ================= Same kind of functionality as of fc21 Additional info: ================ Please note that I'm still concurrently accessing gmail with no problems on machines with fc21 and on F22 machines with other MUAs. Today it seems to be gone especially bonkers and even mail won't work at all. I don't know if google changed anything. Bu the same accounts on Thunderbird are still ok. I'm including a few pictures with the errors I get.
I add that recreating the account just now made the mail part work again, but the calendar is still not working.
sorry. Wherever I wrote "calendar" I meant "Contacts"...
Created attachment 1037337 [details] PNG Screen Grabs of Error Messages
I confirm that I also am having problems with the contacts. When I go to the contacts for the first time, I'm seeing the following error message: Unable to open address book This address book cannot be opened. This either means that an incorrect URI was entered, or the server is unreachable. Detailed error message: Unable to connect to 'Google': The requested resource was not found: https://developers.google.com/accounts/docs/AuthForInstalledApps
It's interesting to note that at that page google says: Important: ClientLogin has been officially deprecated since April 20, 2012 and is now no longer available. Requests to ClientLogin will fail with a HTTP 404 response. We encourage you to migrate to OAuth 2.0 as soon as possible.
Thanks for a bug report. I do not speak (neither read) the language the screenshots are taken in, but I suppose those mentioning "org.gnome.OnlineAccounts" mean something about an issue to get password for the given account [1]. That's the cause of the other issues you see. Please go to Settings->Online Accounts and verify that the Google account doesn't require your attention, there will be shown an exclamation mark if it does. You might re-sign for the account to make it work again. Once the OAuth2 credentials will be refresh evolution will continue to work as expected. [1] If it claims anything about an issue to actually contact the service, then the problem is even deeper, in the goa-daemon, which is supposed to be auto-started after login
(In reply to Kevin L. Mitchell from comment #4) > I confirm that I also am having problems with the contacts. When I go to > the contacts for the first time, I'm seeing the following error message: > > Unable to open address book > > This address book cannot be opened. This either means that an incorrect > URI was entered, or the server is unreachable. > > Detailed error message: Unable to connect to 'Google': The requested > resource was not found: > https://developers.google.com/accounts/docs/AuthForInstalledApps This is different thing, see bug #1226310.
Hi Milan, after creating and destroying the account a few times I verified that the imap part of the account will indeed work correctly if and only if contacts and calendar are not enabled. Whereas if you do enable contacts and calendar imap too will start acting weird. In particular, at least with the accounts I'm testing on, imap will work perfectly just after the account have been configured in evolution and the aforementioned problems will begin the first time evolution is restarted or after a few hours if evolution is left running on its own (eg. I left it running overnight and woke up to the problem).
Thanks for the pointer. I tried to reproduce this and I was able to do it. I found a close-enough bug report in the upstream bugzilla [1], thus I'm going to use it for any further comments. Just note that this will be fixed in 3.16.4+, though it'll require re-addition of the GMail account to correct the underground mess. [1] https://bugzilla.gnome.org/show_bug.cgi?id=750148
evolution-data-server-3.16.3-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/evolution-data-server-3.16.3-2.fc22
Just tested it and it seems to work well now.
Package evolution-data-server-3.16.3-2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing evolution-data-server-3.16.3-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9934/evolution-data-server-3.16.3-2.fc22 then log in and leave karma (feedback).
(In reply to Davide Repetto from comment #11) > Just tested it and it seems to work well now. Nice, thanks for the confirmation.
evolution-data-server-3.16.3-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
The problem is there again since yesterday with this releases: evolution-data-server-3.16.3-2.fc22.x86_64 evolution-3.16.3-2.fc22.x86_64 Maybe google changed something again?
Same problem here. I've tried with gnome online accounts, and configuring with evolution. i'll try and trash .evolution/*
(In reply to Milan Crha from comment #9) > ...Just note that this will be fixed in 3.16.4+, though it'll require > re-addition of the GMail account to correct the underground mess. The above is crucial. I made an update for evolution-data-server, 3.16.3-2, which contains the fix, but only installing it isn't enough, one should re-login (or restart) the machine and then remove the GMail account in Evolution and add it again. (In reply to Davide Repetto from comment #15) > The problem is there again since yesterday with this releases: > evolution-data-server-3.16.3-2.fc22.x86_64 > evolution-3.16.3-2.fc22.x86_64 > > Maybe google changed something again? Just in case, what is the exact error message, please? I suppose you made all the things as described above, also because it did work properly for you earlier.
I had this. I nuked ~/.config/evolution and ~/.local/share/evolution. I reconfigured everything. It worked. I restarted evolution a couple of times. It worked. Then my network connection got reset (outside factors) Now evolution just gets timeouts: "Failed to obtain an access token for ...@gmail.com: timeout was reached" tcpdump shows network connections to port 993. Some traffic flows back and forth. That needed a bounce of goa-daemon to fix the timeout problem.
What's your gnome-online-accounts version, please? $ rpm -q gnome-online-accounts
gnome-online-accounts-3.16.3-1.fc22.x86_64 I've triggered it with two separate network disruptions: 1. Corporate network move from wireless to wired. This uses the same IP range, resolver, etc. but a different IP number. 2. Suspend at work / un-suspend at home. Both times goa-daemon --replace "fixed" evolution. Speculation: Evolution times out after a few seconds, which might not be long enough for GOA to realise the network connection has been interrupted.
This is still a problem. I too had to do: usr/libexec/goa-daemon --replace& To get it to at least temporarily work. evolution-data-server-3.16.5-1.fc22.x86_64 evolution-help-3.16.5-3.fc22.noarch evolution-ews-3.16.5-1.fc22.x86_64 evolution-3.16.5-3.fc22.x86_64 gnome-online-accounts-3.16.4.1-1.fc22.x86_64
I still have the same problem with these versions. gnome-online-accounts-3.16.5-1.fc22.x86_64 evolution-data-server-3.16.5-1.fc22.x86_64 evolution-3.16.5-3.fc22.x86_64 evolution-ews-3.16.5-1.fc22.x86_64 evolution-help-3.16.5-3.fc22.noarch /usr/libexec/goa-daemon --replace& allows to reconnect.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.