@Clint: the only steps required for reproducing this bug is having a Google account configured in the Online Accounts applet in the System Settings. Once the account is configured, several programs including Empathy (the chat) and the Unity Dash search will make use of it automatically. Normally, the user will not be asked to reauthenticate the Google account, at least not before a month has expired since the account was created (or authenticated last): the chat would work whenever one needs, and searching in the Dash would just work. However, when this bug occurs, the user will be asked to reauthenticate the Google account. It's hard to tell when that happens; as you see, different users have reported different times and situations; I myself did not experience this problem at all. It might depend on the user's geographic location, or any funny logic in Google's servers.
I'll check once again about the account-plugins upload. -- 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: Confirmed Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Confirmed Status in “signon-plugin-oauth2” source package in Quantal: Confirmed 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
