Hi, I'm posting my personal case history hoping this can be useful.
I had two laptops both running Ubuntu12.04 (Gnome, w/o Unity). One of them -
Acer - equipped by 32 bits version, the other - Asus - whith 64 bits version.
No troubles with both even when authenticating at the same time to my google
account. Both never asked me for authorization.
In both laptop I used the "contact" application to keep my google contacts.
Everything was fine.
Now I upgraded Asus to 14.04 (64Bit, of course). This kept about a couple oh
hours then everithing was fine, with the exception of a few details I solved in
the next hours.
Now the situation is as follows:
32 Bits 12.04 Acer everithing is fine, never asks for auth to my google
account. Contacts into the application are fine as ever.
64 Bits 14.04 Asus asks me auth every time I log on, and my contacts are
empty, even after hours from logon. Google account appears in the menu and it
is correctly chosen as contacs source ("Rubrica" in italian).
This situation is up to date at 30/08/2014. Both Ubuntu installations updated
and upgraded.
Hoping this can help developers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-plugin-oauth2 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 “evolution-data-server” package in Ubuntu:
Confirmed
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
