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

Issue 775628 link

Starred by 7 users
Status: Verified
Owner:
█ bartfab@chromium.org
Working on ARC now
Closed: Oct 2017
Cc:
█ nkostylev@google.com
khmel@chromium.org
█ bartfab@chromium.org
avkodipelli@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

"Chrome Device Manager has stopped" error

Project Member Reported by kathrelk...@chromium.org, Oct 17 2017 
10040.0.0, lili

When logging into ARC++, see an error popup "Chrome Device Manager has stopped".  After clicking "Open app again", the Google Play Terms of Service window continues to spin.  Eventually reach a "Something went wrong" screen.

Happens every time, with multiple domains.

M64
10040.0.0 (4397007), veyron_minnie, FAIL

M63
10032.4.0 (4397326), lars, FAIL
10032.0.0 (4394138), veyron_minnie, FAIL
10026.0.0 (4391817), veyron_minnie, PASS
10022.0.0 (4385092), veyron_minnie, PASS

Comment 1 by kathrelk...@chromium.org, Oct 17 2017

Screenshot 2017-10-17 at 11.51.32 AM.png
1.1 MB View Download
Screenshot 2017-10-17 at 11.53.48 AM.png
1.2 MB View Download
debug-logs_20171017-115431.tgz
21.5 MB Download

Comment 2 by kathrelk...@chromium.org, Oct 17 2017

Cc: nkostylev@google.com
Confirmed broken on 10030.0.0

That puts the break between Android builds 4391817 and 4394016, making CloudDPC releases v61700 or v61800 the likely culprits.

Comment 3 by gkihumba@google.com, Oct 17 2017

Owner: bhthompson@chromium.org
Status: Assigned (was: Untriaged)
Bernie could you please assign the right owner for this...thanks

Comment 4 by bhthompson@google.com, Oct 17 2017

Cc: khmel@chromium.org
Owner: bartfab@chromium.org
I think this is in bartfab's jurisdiction?

Comment 5 by khmel@chromium.org, Oct 17 2017 

Dup: b/67854746

Comment 6 by kathrelk...@chromium.org, Oct 17 2017 

Leaving open to make sure we block releases on this.

Comment 7 by gkihumba@google.com, Oct 18 2017

Cc: avkodipelli@chromium.org
According to Avinash, this only affects enterprise devices, so not blocking dev on it.

Comment 8 by kathrelk...@chromium.org, Oct 18 2017

Labels: -ReleaseBlock-Dev ReleaseBlock-Beta
I'm willing to slip to Beta blocking

Comment 9 by kathrelk...@chromium.org, Oct 19 2017

Status: Verified (was: Assigned)
Fixed in 10046.0.0
Project Member

Comment 10 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Oct 19 2017

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-63; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-63 label, otherwise remove Merge-TBD label. Thanks.

Comment 11 by kathrelk...@chromium.org, Oct 19 2017

Labels: -Merge-TBD
Working in M-63 as of 10032.7.0

Comment 12 by songsuk@chromium.org, Oct 20 2017

Status: Assigned (was: Verified)
Able to reproduce the issue on Chrome 63.0.3239.13/CrOS 10032.8.0 - Reks

Comment 13 by kathrelk...@chromium.org, Oct 20 2017

Status: Verified (was: Assigned)
Unfortunately 10032.8.0 brings us https://buganizer.corp.google.com/issues/68049955, which breaks Play Store on all Intel devices, regardless of Enterprise.

Closing this bug again.
Project Member

Comment 14 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Oct 20 2017

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-63; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-63 label, otherwise remove Merge-TBD label. Thanks.

Comment 15 by kathrelk...@chromium.org, Oct 20 2017

Labels: -Merge-TBD
►

Sign in to add a comment