@Alberto: I did a few tests, and it looks like my accounts are going completely crazy. Maybe it's my home folder's fault, with files dating back to the old dapper drake :D However, the login request appears with at least one between evolution contacts, evolution gmail, evolution calendar, empathy, shotwell enabled. If I enable one of them, the request appears immediately. Obviuosly I always gave access before logging out. The login request is in the form illustrated by the attached screenshot: a new window appears, and usually I have to enter my credentials in the main window; every now and then the main window appears black, and the form is in the secondary window. I use the two-step authentication from google, and the first time I added the account it opened a google page in the main window and I had to enter the token from the google auth app.
** Attachment added: "Funny login screen" https://bugs.launchpad.net/account-plugins/+bug/1029289/+attachment/3779398/+files/Bug%20google%20account%20-%20screen1.png -- 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
