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

Issue 735523 link

Starred by 4 users
Status: Duplicate
Merged: issue 735471
Owner:
█ roc...@chromium.org
please use my google.com address
Closed: Jun 2017
Cc:
█ ben@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Cloud Print Service cannot register new printers

Project Member Reported by thestig@chromium.org, Jun 21 2017 
Chrome Version: 59.x
OS: Windows

What steps will reproduce the problem?
(1) Install Chrome
(2) Download and install https://tools.google.com/dlpage/cloudprintservice
(3) Run the Cloud Print Service and try to register a printer

What is the expected result?

Printer is registered and shows up on https://www.google.com/cloudprint#printers

What happens instead?

Printer never shows up.

I haven't finished bisecting yet, but my suspect is r458954.

Comment 1 by thestig@chromium.org, Jun 21 2017 

It's r458954. Let me know if you need help debugging / testing this one.

Comment 2 by roc...@chromium.org, Jun 21 2017 

Thanks, I'll get a repro environment set up ASAP.

Comment 3 by roc...@chromium.org, Jun 21 2017 

Can you please remind me what the best workflow is for testing a local chrome change here?

Do I need a Google branded build? I also recall there being some mini-installer target?

Comment 4 by thestig@chromium.org, Jun 21 2017 

I'm testing with the Google branded mini-installer.

Comment 5 by roc...@chromium.org, Jun 21 2017

Cc: -roc...@chromium.org
Owner: roc...@chromium.org
Status: Started (was: Untriaged)

Comment 6 by roc...@chromium.org, Jun 21 2017 

FWIW this does not appear to be an issue on ToT. With the fix to  bug 735471  applied, I can start the GCP service *and* register printers.

I'm going to test the fix in M60 next.

Comment 7 by roc...@chromium.org, Jun 22 2017

Mergedinto: 735471
Status: Duplicate (was: Started)
I have confirmed that the fix for  bug 735471  fixes everything. So there was probably a broken state in M59 before it actually branched and that's what this other bisect found. Closing as a dupe to at least preserve some bug tracking state between these two things.
►

Sign in to add a comment