| 2016-12-14 19:21:39 |
Jeremy Bícha |
bug |
|
|
added bug |
| 2016-12-14 19:21:54 |
Jeremy Bícha |
nominated for series |
|
Ubuntu Yakkety |
|
| 2016-12-14 19:21:54 |
Jeremy Bícha |
bug task added |
|
gnome-online-accounts (Ubuntu Yakkety) |
|
| 2016-12-14 20:05:59 |
Jeremy Bícha |
bug watch added |
|
https://bugzilla.gnome.org/show_bug.cgi?id=774202 |
|
| 2016-12-14 20:05:59 |
Jeremy Bícha |
bug task added |
|
gnome-online-accounts |
|
| 2016-12-14 20:58:12 |
Bug Watch Updater |
gnome-online-accounts: status |
Unknown |
Fix Released |
|
| 2016-12-14 20:58:12 |
Bug Watch Updater |
gnome-online-accounts: importance |
Unknown |
Medium |
|
| 2016-12-14 21:46:06 |
Jeremy Bícha |
description |
Impact
======
Some bugs in evolution-data-server were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example).
This update changes the API key used by those using the GNOME Online Accounts feature.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This update depends on the pending evolution-data-server 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of evolution-data-server so we don't taint the new keys too!
Also, Evolution has two ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server has its own Google authentication method. The evolution-data-server key probably will similarly need to be updated. |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This update depends on the pending evolution-data-server 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of evolution-data-server so we don't taint the new keys too!
Also, Evolution has two ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server has its own Google authentication method. The evolution-data-server key probably will similarly need to be updated. |
|
| 2016-12-15 16:12:17 |
Jeremy Bícha |
description |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This update depends on the pending evolution-data-server 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of evolution-data-server so we don't taint the new keys too!
Also, Evolution has two ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server has its own Google authentication method. The evolution-data-server key probably will similarly need to be updated. |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This update depends on the pending evolution-data-server 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of evolution-data-server so we don't taint the new keys too!
Also, I believe Evolution has three ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own Google authentication method 3) Ubuntu Online Accounts.
The errors are much less common for the e-d-s API key so upstream does not intend to change that key. The e-d-s key is new, only existing in Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3 Staging PPA since --disable-google-auth is used there to not add a new universe dependency.)
See LP: #1650007 for whether this affects the Ubuntu Online Accounts key. |
|
| 2016-12-16 11:46:40 |
Jeremy Bícha |
gnome-online-accounts (Ubuntu): status |
New |
Fix Released |
|
| 2016-12-16 11:46:50 |
Jeremy Bícha |
gnome-online-accounts (Ubuntu Yakkety): importance |
Undecided |
High |
|
| 2016-12-16 11:46:55 |
Jeremy Bícha |
gnome-online-accounts (Ubuntu Yakkety): status |
New |
In Progress |
|
| 2016-12-16 11:51:30 |
Jeremy Bícha |
description |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This update depends on the pending evolution-data-server 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of evolution-data-server so we don't taint the new keys too!
Also, I believe Evolution has three ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own Google authentication method 3) Ubuntu Online Accounts.
The errors are much less common for the e-d-s API key so upstream does not intend to change that key. The e-d-s key is new, only existing in Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3 Staging PPA since --disable-google-auth is used there to not add a new universe dependency.)
See LP: #1650007 for whether this affects the Ubuntu Online Accounts key. |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This update depends on the pending evolution-data-server (e-d-s) 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of e-d-s so we don't taint the new keys too!
We can't fix this for Ubuntu 16.04 LTS until we figure out how to backport the needed e-d-s changed there.
I believe Evolution has three ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own Google authentication method 3) Ubuntu Online Accounts.
The errors are much less common for the e-d-s API key so upstream does not intend to change that key. The e-d-s key is new, only existing in Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3 Staging PPA since --disable-google-auth is used there to not add a new universe dependency.)
Similarly, Ubuntu Online Accounts does not currently appear to be impacted (LP: #1650007). |
|
| 2017-01-12 20:47:57 |
Jeremy Bícha |
description |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This update depends on the pending evolution-data-server (e-d-s) 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of e-d-s so we don't taint the new keys too!
We can't fix this for Ubuntu 16.04 LTS until we figure out how to backport the needed e-d-s changed there.
I believe Evolution has three ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own Google authentication method 3) Ubuntu Online Accounts.
The errors are much less common for the e-d-s API key so upstream does not intend to change that key. The e-d-s key is new, only existing in Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3 Staging PPA since --disable-google-auth is used there to not add a new universe dependency.)
Similarly, Ubuntu Online Accounts does not currently appear to be impacted (LP: #1650007). |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This was fixed in zesty in gnome-online-accounts 3.22.3-1.
This update depends on the pending evolution-data-server (e-d-s) 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of e-d-s so we don't taint the new keys too!
We can't fix this for Ubuntu 16.04 LTS until we figure out how to backport the needed e-d-s changed there.
I believe Evolution has three ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own Google authentication method 3) Ubuntu Online Accounts.
The errors are much less common for the e-d-s API key so upstream does not intend to change that key. The e-d-s key is new, only existing in Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3 Staging PPA since --disable-google-auth is used there to not add a new universe dependency.)
Similarly, Ubuntu Online Accounts does not currently appear to be impacted (LP: #1650007). |
|
| 2017-01-12 20:53:41 |
Brian Murray |
gnome-online-accounts (Ubuntu Yakkety): status |
In Progress |
Fix Committed |
|
| 2017-01-12 20:53:43 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-01-12 20:53:45 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-01-12 20:53:48 |
Brian Murray |
tags |
yakkety zesty |
verification-needed yakkety zesty |
|
| 2017-01-12 20:58:00 |
Jeremy Bícha |
description |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This was fixed in zesty in gnome-online-accounts 3.22.3-1.
This update depends on the pending evolution-data-server (e-d-s) 3.22.3 SRU (LP: #1639926) since we need to make sure the user has a fixed version of e-d-s so we don't taint the new keys too!
We can't fix this for Ubuntu 16.04 LTS until we figure out how to backport the needed e-d-s changed there.
I believe Evolution has three ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own Google authentication method 3) Ubuntu Online Accounts.
The errors are much less common for the e-d-s API key so upstream does not intend to change that key. The e-d-s key is new, only existing in Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3 Staging PPA since --disable-google-auth is used there to not add a new universe dependency.)
Similarly, Ubuntu Online Accounts does not currently appear to be impacted (LP: #1650007). |
Impact
======
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors for those using Google services with evolution-data-server and apps that use it (Evolution is a prominent example). Unfortunately, it looks like users using older versions of e-d-s are causing those errors to affect everyone using e-d-s since they are using the same API key. It's very difficult for GNOME to push everyone to use an updated version of their software.
Therefore, this update changes the API key used by those using the GNOME Online Accounts feature for Google services.
Test Case
=========
Restart your computer after applying the updates.
Then use Evolution with a Google account configured by gnome-control-center's Online Accounts. The easiest way to configure that correctly is to use Ubuntu GNOME.
Make sure that Evolution works without getting authentication errors with your Google services.
Regression Potential
====================
I think the only possibility for regression is if GNOME did not configure the key correctly with Google's developer platform.
Other Info
==========
This was fixed in zesty in gnome-online-accounts 3.22.3-1.
This update depends on the evolution-data-server 3.22.3 SRU (LP: #1639926) (now in yakkety-updates and fully phased) since we need to make sure the user has a fixed version of e-d-s so we don't taint the new keys too!
We can't fix this for Ubuntu 16.04 LTS until we figure out how to backport the needed e-d-s changed there.
I believe Evolution has three ways to use Google services: 1) GNOME Online Accounts 2) evolution-data-server (e-d-s) has its own Google authentication method 3) Ubuntu Online Accounts.
The errors are much less common for the e-d-s API key so upstream does not intend to change that key. The e-d-s key is new, only existing in Ubuntu 16.10 and above. (It's not even used in the Ubuntu 16.04 GNOME3 Staging PPA since --disable-google-auth is used there to not add a new universe dependency.)
Similarly, Ubuntu Online Accounts does not currently appear to be impacted (LP: #1650007). |
|
| 2017-02-01 09:29:51 |
Jeremy Bícha |
tags |
verification-needed yakkety zesty |
verification-done yakkety zesty |
|
| 2017-02-02 16:40:27 |
Launchpad Janitor |
gnome-online-accounts (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-02-02 16:40:35 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
