User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 SeaMonkey/2.53 Build ID: 20180402185612 Steps to reproduce: Upgraded to TB 60.0b6 and Lightining 6.2b6 / GData Provider 4.1b6. Did not see this with TB 60.0b5 and Lightining 6.2b5 / GData Provider 4.1b5. Actual results: I have two accounts, one GMail one business Google Mail account, both OAuth2. When I close TB and open it, it prompts from the GMail account credentials for calendar. I got through the normal acceptance for TB to manage the calendar. If I close and re-open TB again, it prompts for my other Google Mail account credentials. I got through the normal acceptance for TB to manage the calendar. If I close and re-open TB, it will ask again for the credentials for the GMail account but not the Google Mail account. Seems to remember one account, and then forget the other and alternating between the two if TB is closed and re-opened. Expected results: It should not prompt to remember calendar credentials once allowed to manage a calendar.

I'm leaning towards bustage in either the Lightining 6.2b6 / GData Provider 4.1b6 components as my work PC was upgraded to TB 60.0b6 but is running Lightining 6.2b3 / GData Provider 4.1b3 and it is not prompting me as in the STR. Want me to try anything?

So I had a moment to test on my home PC. I reverted Lighting back to 6.2b3 and it no longer ask repeatedly for credentials to my calendars. GData Provider 4.1b6 is still installed so something after Lightning 6.2b3 caused the bustage.

Karl or Chris, can you reproduce this

I don't use GData Provider. I'm having trouble finding the proper versions of the providers and lightning 6.2b6 to try to reproduce.

(In reply to Karl Rossing from comment #4) > I don't use GData Provider. I'm having trouble finding the proper versions > of the providers and lightning 6.2b6 to try to reproduce. They're here: http://ftp.mozilla.org/pub/calendar/lightning/candidates/

All, I cloned bug 1301422 as bug 1470424 as this is basically just a repeat of that bug anyway but with the issue being Provider for Google Calendar specific. Please use bug 1470424 instead.