New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 695575 link

Starred by 1 user
Status: Duplicate
Merged: issue 688532
Owner:
█ keta...@chromium.org
Last visit > 30 days ago
Closed: Feb 2017
Cc:
█ mu...@chromium.org
rohi...@chromium.org
ihf@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Component updates will often cause a double update

Project Member Reported by abodenha@chromium.org, Feb 23 2017 
Consider the following case:
1: Machine is on M55 stable
2: Latest stable is 56
3: There's a flash update targeted to 56

What's happening right now is that the user sees an update notification, restarts, and then very quickly after coming back gets ANOTHER update notification and has to restart again.  This is really annoying when it happens.

I just got hit by what I think is this case and I've been seeing reports of it from users.

Comment 1 by abodenha@chromium.org, Feb 23 2017 

Just confirmed.
* Got an update to 57.0.2987.59-beta
* Almost immediately got another update notification (this one orange which implies that it's more urgent. Misleading since the second update blocked on the first.)
* After the second update the only difference is that flash version has changed from 24.0.0.221 to 25.0.0.113

Comment 2 by ketakid@google.com, Feb 23 2017

Mergedinto: 688532
Status: Duplicate (was: Assigned)
This is a dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=688532. This is being caused by the COmponent updater for flash. We just moved to Beta in m57.

Comment 3 by ihf@chromium.org, Feb 23 2017 

This problem should be M57 only as in #1 (not M56 as initial report).
►

Sign in to add a comment