Thanks a lot, David and Damiano! Your cases seem to be different: @Damiano: it looks like there is some application which asks to authenticate with Google using the plain password method, and that's what generating the error. In fact, from your logs I can see that the OAuth authentication went on successfully at 13:22:16 and at 13:22:54, but then at 13:23:00 the "password" method was used. Since you can reproduce the bug fairly easily, could you please try disabling evolution from the Online Accounts panel, logout and then in again? If you could try that for contacts, mail and calendar one at a time this would help us find the issue (I'd bet it's the calendar). Anyway, when you click on the account to reauthenticate, does it directly show a form with username and password, or does it send you to the Google website?
@David: I know this is quite annoying, but do you think you can disable the Facebook and the MSN/Live accounts and try again? Since they all authenticate at the same time, and using the same method (Oauth), it's impossible to follow the logs. :-( Also, how often does this happen? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Bug description: [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
