Activity log for bug #1637957

Date Who What changed Old value New value Message
2016-10-31 09:55:45 Alberto Donato bug added bug
2016-10-31 16:58:38 Launchpad Janitor chromium-browser (Ubuntu): status New Confirmed
2016-11-05 03:12:13 Alberto Salvia Novella chromium-browser (Ubuntu): importance Undecided Medium
2016-11-05 03:12:18 Alberto Salvia Novella chromium-browser (Ubuntu): importance Medium High
2016-11-05 03:12:30 Alberto Salvia Novella nominated for series Ubuntu Yakkety
2016-11-05 03:12:30 Alberto Salvia Novella nominated for series Ubuntu Xenial
2016-11-05 03:15:34 Alberto Salvia Novella chromium-browser (Ubuntu): status Confirmed Triaged
2016-11-15 04:47:58 Chen-Han Hsiao (Stanley) bug added subscriber Chen-Han Hsiao (Stanley)
2017-01-13 21:47:33 Patrick Noland branch linked lp:~chromium-team/chromium-browser/yakkety-working
2017-01-13 21:49:25 Patrick Noland bug added subscriber Chad Miller
2017-01-13 21:49:52 Patrick Noland bug added subscriber Patrick Noland
2017-01-13 22:05:54 Alberto Donato description In Chromium 53 (tested on Xenial and Yakkety) sync setup fails if the account login goes through SAML authentication (the setup fails after a successful SAML login). Apparently this is fixed in release 54, see https://bugs.chromium.org/p/chromium/issues/detail?id=655960 and https://bugs.chromium.org/p/chromium/issues/detail?id=571001 for details about the bug. Would it be possible to SRU the new version? Sync login is failing with SAML authentication. See https://bugs.chromium.org/p/chromium/issues/detail?id=677154 for details.
2017-01-19 16:58:23 Alberto Donato chromium-browser (Ubuntu): status Triaged Fix Released
2017-01-19 16:58:33 Alberto Donato chromium-browser (Ubuntu): status Fix Released Confirmed
2017-01-20 16:54:24 Alberto Donato chromium-browser (Ubuntu): status Confirmed Fix Released