Description of problem: When trying to add a Google account, after authenticating it reports "Credentials have expired. Sign in to enable this account". Trying to sign in again results in no change. This was working at some earlier point on F23, it may have been broken by the F24 upgrade. Aside from the actual bug, this isn't appropriate UI behavior. If it can't authenticate properly it should report some useful information to the user. Version-Release number of selected component (if applicable): gnome-online-accounts-3.20.1-1.fc24.x86_64 How reproducible: Every time (for me) Steps to Reproduce: 1. Add Google account (it is using two-factor authentication) 2. Enter password and authentication code, and allow access from GNOME app 3. Actual results: Can't connect and reports credentials expired Expected results: Account logs in properly Additional info: When trying to open Google Drive, it reports "Invalid credentials". I noticed this output in journalctl. Some kind of Google API key problem? Jun 27 23:51:59 haswell gvfsd[1425]: ** (process:19166): WARNING **: Authentication required: { Jun 27 23:51:59 haswell gvfsd[1425]: "error": { Jun 27 23:51:59 haswell gvfsd[1425]: "errors": [ Jun 27 23:51:59 haswell gvfsd[1425]: { Jun 27 23:51:59 haswell gvfsd[1425]: "domain": "usageLimits", Jun 27 23:51:59 haswell gvfsd[1425]: "reason": "dailyLimitExceededUnreg", Jun 27 23:51:59 haswell gvfsd[1425]: "message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.", Jun 27 23:51:59 haswell gvfsd[1425]: "extendedHelp": "https://code.google.com/apis/console" Jun 27 23:51:59 haswell gvfsd[1425]: } Jun 27 23:51:59 haswell gvfsd[1425]: ], Jun 27 23:51:59 haswell gvfsd[1425]: "code": 403, Jun 27 23:51:59 haswell gvfsd[1425]: "message": "Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup." Jun 27 23:51:59 haswell gvfsd[1425]: } Jun 27 23:51:59 haswell gvfsd[1425]: } Jun 27 23:51:59 haswell gvfsd[1425]: ** (gvfsd:1425): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Permission denied
After a reboot it seems to work fine now. I don't really have an explanation for why it changed, though it did take a long time to reboot so maybe some process was hung up. Still seems like user feedback needs to be improved at the very least.
Spoke too soon. It was working, but then quickly stopped working again in the same manner, though Google Drive doesn't show the "daily limit exceeded" error at this point. Empathy prints this on its output when it tries to connect: (empathy:5393): folks-WARNING **: Error preparing persona store 'eds:1467092161.1688.16@haswell': Couldn't open address book ‘1467092161.1688.16@haswell’: Unable to connect to 'Contacts': Failed to obtain an access token for 'Contacts': Failed to retrieve credentials from the keyring
I have similar problem with current F24 and it's probably long-lasting bug - https://bugzilla.redhat.com/show_bug.cgi?id=751094 All credentials seems to be "expired" when I logout and then login (after fall of X11, switching to another user, etc.) Temporary workaround is to kill goa-deamon. It works fine after it respawns.
(In reply to David Novák from comment #3) > I have similar problem with current F24 and it's probably long-lasting bug - > https://bugzilla.redhat.com/show_bug.cgi?id=751094 > > All credentials seems to be "expired" when I logout and then login (after > fall of X11, switching to another user, etc.) > > Temporary workaround is to kill goa-deamon. It works fine after it respawns. Killing goa-daemon is not enough in my case, Evoluton's factories also have to be killed. gnome-online-accounts-3.20.4-1.fc24.x86_64 evolution-ews-3.20.5-1.fc24.x86_64 evolution-data-server-3.20.5-5.fc24.x86_64 evolution-3.20.5-1.fc24.x86_64 evolution-help-3.20.5-1.fc24.noarch
I see this problem in Evolution. Every so often it will be unable to access my google calendar. When I go to settings and try to sign in again, the login process never seems to work, and the settings program gives no useful error message that I can see. I can at least get evolution to work again by going to a command line: nohup /usr/libexec/goa-daemon --replace &
Created attachment 1213747 [details] Screenshot of Empathy not working I experience the same problem with Evolution, randomly not being able to retrieve login data from keyring. However in empathy it is always not working. It is worth noting that in goa settings screen I have no "chat" option anymore.
Same problem in FC25: evolution-help-3.22.1-2.fc25.noarch evolution-data-server-3.22.1-1.fc25.x86_64 evolution-3.22.1-2.fc25.x86_64 evolution-ews-3.22.1-1.fc25.x86_64 Killing and starting manually goa-daemon sometimes help, sometimes goa-daemon is not started on login: []$ killall goa-deamon goa-deamon: no process found []$ /usr/libexec/goa-daemon --replace & [1] 22846 []$ goa-daemon-Message: goa-daemon version 3.22.1 starting
This bug seems to exist since F11 and was filed time and time again for multiple versions. There are also occurances of the same problem with non-google accounts. For me it is F24 and the same versions as stated before.
I have the same issue in F25. I faced it in the past already, then it worked for long time and it is back again now. Really annoying issue. gnome-online-accounts-3.22.1-1.fc25.x86_64
Same problem here on F25. Restarting goa-daeom helps sometimes. Evolution doesn't connect to IMAP or Google or OwnCloud. gnome-online-accounts.x86_64 3.22.1-1.fc25
I see the bug across different accounts and distros. During the day I use F25 and the message starts to appear around 7pm EST. In the evening I switch to a machine running Gentoo (evolution 3.22.2) and a different google account and the error is there since I first open evolution.
(In reply to Jan Vesely from comment #11) > I see the bug across different accounts and distros. During the day I use > F25 and the message starts to appear around 7pm EST. In the evening I switch > to a machine running Gentoo (evolution 3.22.2) and a different google > account and the error is there since I first open evolution. sorry, wrong bug. ignore my comment.
Repro top with goa-daemon load on cpu during sync after launching errorless/null populated Gnome Calendar autostart. Checked with Evolution 3.22 launch. Errors displayed below. Sync activity on network appears to blow past Googles "quota allowance". Layman suggestion to increment conservative syncs as needed rather than waiting 24hrs to refresh what looks to be the whole accounts content. Evolution 3.22.1 error on launch: <snip> Failed to login to the server: Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav/quotas?project=923794261470
Looks like bug 1340203 To confirm: check if you can reproduce when you log out/in, but not if you reboot.
For me log out / in does not help. Sometimes rebooting is not helping as well.
Have come upon this as well after upgrading to FC25. For the time being I've deleted GOA defs and locally defined Google accounts to Evolution.
My newest observation (I'm not a developer, nor I know anything about Google API, not sure if relevant). When the issue occurs, I try to open Tasks (linked to Google). The following error is displayed my Evolution: Unable to connect to 'Tasks': Cannot open calendar: Authentication required: { "error": { "errors": [ { "domain": "usageLimits", "reason": "dailyLimitExceeded", "message": "Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/tasks/quotas?project=923794261470", "extendedHelp": "https://console.developers.google.com/apis/api/tasks/quotas?project=923794261470" } ], "code": 403, "message": "Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/tasks/quotas?project=923794261470" } } Trying to see the quota on the console, I am getting: 'The API "tasks" doesn't exist or you don't have permission to access it'. After quitting Evolution and killing as follows: [pasiasty@lilith3-localdomain ~]$ killall evolution-addressbook-factory evolution-calendar-factory evolution-source-registry goa-daemon goa-identity-service I'm still getting the same error messages.
Multiple different bugs are mixed up here. (In reply to Robert Hancock from comment #1) > After a reboot it seems to work fine now. I don't really have an explanation > for why it changed, though it did take a long time to reboot so maybe some > process was hung up. > > Still seems like user feedback needs to be improved at the very least. That is bug 1340203. (In reply to Cezary Zemis from comment #17) > My newest observation (I'm not a developer, nor I know anything about Google > API, not sure if relevant). > > When the issue occurs, I try to open Tasks (linked to Google). The following > error is displayed my Evolution: > > Unable to connect to 'Tasks': Cannot open calendar: Authentication required: > { > "error": { > "errors": [ > { > "domain": "usageLimits", > "reason": "dailyLimitExceeded", > "message": "Daily Limit Exceeded. The quota will be reset at midnight > Pacific Time (PT). You may monitor your quota usage and adjust limits in the > API Console: > https://console.developers.google.com/apis/api/tasks/ > quotas?project=923794261470", > "extendedHelp": > "https://console.developers.google.com/apis/api/tasks/ > quotas?project=923794261470" > } > ], > "code": 403, > "message": "Daily Limit Exceeded. The quota will be reset at midnight > Pacific Time (PT). You may monitor your quota usage and adjust limits in the > API Console: > https://console.developers.google.com/apis/api/tasks/ > quotas?project=923794261470" > } > } > > Trying to see the quota on the console, I am getting: 'The API "tasks" > doesn't exist or you don't have permission to access it'. > > After quitting Evolution and killing as follows: > [pasiasty@lilith3-localdomain ~]$ killall evolution-addressbook-factory > evolution-calendar-factory evolution-source-registry goa-daemon > goa-identity-service > I'm still getting the same error messages. The root cause is a series of evolution-data-server bugs. See: https://debarshiray.wordpress.com/2016/12/15/new-gnome-api-key-for-google-services/
*** This bug has been marked as a duplicate of bug 1385825 ***