gnome-calendar keeps asking for my google password

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Status changed to 'Confirmed' because the bug affects multiple users.

According to the Gmail email notice I received:
"Google will continue to block sign-in attempts from the app you're using because it has known security problems or is out of date. You can continue to use this app by allowing access to less secure apps, but this may leave your account vulnerable."

I just upgraded from 17.04 to 17.10 today and am experiencing the issue as described. One thing not previously mentioned by others: I have two factor auth enabled on my account. I was never asked for the 2nd auth, yet I still see my calendar data being updated.

doug are you sure you didn't allow it in online accounts settings?
That's the account and authorization used by calendar, I have 2 factor authentication and when I set it up in online accounts it asked me for the second face auth.
There's no way an app can access your calendar or other info if you have two factor authentication in google.

Else it would be a google bug.

Could it be that I had previously allowed me in due to having performed the second auth before the upgrade? Aside from that, it's possible I performed the auth during the initial stages of the upgrade and don't remember now.

That said, it just seemed strange and potentially relevant that I am repeatedly asked for my Google account login without being asked for an auth code.

Doug that's exactly what the bug says and why I filled it, you are not being asked for the auth code simply because there is a bug in the login. I filled the bug, the annoyance is because the application is asking for a password it doesn't need.

My feeling is that it is using some remanent pre-update account. In response Sebastian Bacher, I don't believe it's an upstream bug, since is generated in the upgrade process, I think the accounts were ill transformed in the upgrade process, either way I generated a bug report in gnome-calendar: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1726922

There is no account conversion on upgrades or anything like that, and yes it's an upstream issue if the code doesn't work as it should

Here is the workaround for people coming into this bug with Two Factor Auth set. You need to generate an application specific password for the Google acct in "Online Accounts" from this page: https://security.google.com/settings/security/apppasswords

Google's full documentation on generating application specific passwords for applications that aren't compatible with MFA: https://support.google.com/accounts/answer/185833?hl=en

I saw this as well, and set an app specific password to get around it, but it would be nice if I didn't have to use that workaround. :)

I'm affected by this issue and do have 2FA enabled, but using an app specific password did not fix the issue. I still get frequent popups.

Well, the workaround that works for me is to toggle off the Calendar in the Search section of the system settings.

On this page

https://askubuntu.com/questions/967137/calendar-constantly-requiring-google-authentication-on-17-10

a solution is suggested:

"I was having the same problem and resolve it by deleting the configuration files of Evolution. Do this:

rm -rf ./.config/goa-1.0/accounts.conf
rm -rf ./.config/evolution
rm -rf ./.local/share/evolution"

Worked for me

I solved it by deleting the calendar. It's on my mobile phone, enough.

Thank you Mat, deleting the config files seems to have worked for me too.

Deleting files in ~/.config is suboptimail in my case;
I have very few applications installed and already have 122 objects in .config.
It would be nice if someone [who knows] told us what variable we are to look for.
that Google seems to be the culprit in virtually all cases here, and that the applicationdoes not report itself whrn invoking this obscurity measure, fails to amaze me.