Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 69.0.3497.81 using Windows 10 with the below mentioned steps.
1. Launched Chrome
2. Tried printing using cloud print .png and .pdf files
We were able to print them properly without any issues. Attaching the screenshot of the same for reference.

@Reporter: Could you please let us know if this is happening with all kinds of files or any specific file? Any further inputs from your end may be helpful.

Deleted: 882158.png 195 KB

	882158.png 195 KB View Download

I encounter the same issue on a Windows 7 machine

Version 69.0.3497.81

The following hapens:
1. I add a legacy printer
2. The printer is shown in the list and it is possible to share the printer
3. If I print (from a different user), the print will stay "in progress" and eventually the printer goes offline. 
4. I tried with different printers. 

We have encountered the same problem printing to legacy printers using Windows 10 and Windows 7.

Chrome version: 69.0.3497.81  Channel: stable
OS Version: Windows 10, Windows 7

Reproduce:
1. Add a legacy printer
2. Print a document; the print job is "In progress" forever, never prints.

I tried with different legacy printers. We only have legacy printers.

Thanks for reporting the issue. Will take a look.

I can reproduce this. It looks the Cloud Print Proxy is crashing. e.g. Crash f6bb94a20cc631dd

Thread 8 (id: 0x42c0) CRASHED [EXCEPTION_BREAKPOINT @ 0x00007ff62dcceeee ]
(chrome.exe -sandbox_policy_base.cc:363 )	sandbox::PolicyBase::AddHandleToShare(void *)
(chrome.dll -sandbox_win.cc:857 )	service_manager::SandboxWin::StartSandboxedProcess(base::CommandLine *,std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,std::vector<void *,std::allocator<void *> > const &,service_manager::SandboxDelegate *,base::Process *)
(chrome.dll -sandbox_init_win.cc:52 )	content::StartSandboxedProcess(content::SandboxedProcessLauncherDelegate *,base::CommandLine *,std::vector<void *,std::allocator<void *> > const &,base::Process *)
(chrome.dll -service_utility_process_host.cc:438 )	ServiceUtilityProcessHost::Launch(base::CommandLine *,bool)
(chrome.dll -service_utility_process_host.cc:405 )	ServiceUtilityProcessHost::StartProcess(bool)
(chrome.dll -service_utility_process_host.cc:310 )	ServiceUtilityProcessHost::StartRenderPDFPagesToMetafile(base::FilePath const &,printing::PdfRenderSettings const &)
(chrome.dll -print_system_win.cc:447 )	cloud_print::`anonymous namespace'::JobSpoolerWin::Core::RenderPDFPagesInSandbox

Still need to track down what's causing this.

+ CloudPrint Test folks

This shouldn't block the upcoming M69 update. I hope to track down the root cause today, and work on the fix this week. Let's try to get the fix merged to M69 in time for the update after the upcoming M69 update.

+rcsantana FYI

paolof: BTW, shouldn't the server eventually realize the print job failed and change the state from "In Progress" to "Error" ?

rockot: Sorry for the bad news. It turned out be r562811 after all. To reproduce:

1) On a Windows machine, visit chrome://devices
2) Go through the add printer set up flow to make the MS XPS Document Writer a Cloud Printer.
3) Print to it via Cloud Print.

Expected: Save As dialog pops up. Saving results in a valid .xps file. Cloud Print Service remains alive.
Actual: Save As dialog pops up. Saving results in a 0 byte .xps file. Cloud Print Service crashes.

I have a set up to reproduce this, so if you have patches for me to try, I can do that.

where can I find version 68 to get my Chromebooks printing again? Downloaded what I thought was ver. 68 and turned off updater in msconfig and it still came up as ver. 69. School is in session and users are desperate.

Looking. Will probably be several hours before I have a fix. We should not block the next 69 respin on this, but will likely still want to merge for the one after that.

Verified fix at https://chromium-review.googlesource.com/c/chromium/src/+/1220266 going though CQ now.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2d480872f3afcc022749c86636b1a28acbe307f5

commit 2d480872f3afcc022749c86636b1a28acbe307f5
Author: Ken Rockot <rockot@chromium.org>
Date: Tue Sep 11 18:06:28 2018

[cloud-print] Fix service utility process launch

Fixes a bug which breaks sandboxed service utility process launching.
The launcher was invalidating the child process's Mojo channel handle
before launch.

Bug:  882158 
Change-Id: I406bc3adcf9be2e74dda87f536151b4f05ac3319
Reviewed-on: https://chromium-review.googlesource.com/1220266
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#590401}
[modify] https://crrev.com/2d480872f3afcc022749c86636b1a28acbe307f5/chrome/service/service_utility_process_host.cc

Pls update bug with canary result tomorrow. Thank you.

I tested at r590401 and that works.

We are having the same issues with legacy printers.  All are offline

This is a very low-risk change which has been verified locally.

I think we should merge ASAP without waiting for Canary results.

This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), kariahda@(iOS), cindyb@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

If you are running Cloud Print for an organization, i.e. with a dedicate Windows print server, the current recommendation is to use the Google Cloud Print Connector instead. See https://github.com/google/cloud-print-connector and https://github.com/google/cloud-print-connector/wiki/Windows-MSI-Installation .

+ jayhlee@ (Enterprise POC) as FYI

@thestig

Is the `cloud-print-connector` the same as https://tools.google.com/dlpage/cloudprintservice windows print service ? as this has the same problem... all jobs stay "In progress" and are not printed.

This is actually our original problem reported by our clients, though I reduced it to straight cloud print in my first report.

re: comment 26, no, "Cloud Print Connector" and "Cloud Print Service" are two different things. The "Cloud Print Service" requires Chrome to be installed, so when Chrome has this bug, "Cloud Print Service" does too. The "Cloud Print Connector" is a standalone program.

@thestig re: comment 27

Ah ok cool, had not yet heard of it, will look in to this tomorrow!

Thanks, Aubrey

Merge approved, M69.

Approving merge to M70 branch 3538, pls merge so we can pick it up for tomorrow's M69 last Dev release. Thank you.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2e005aad2b9b4253e6d39cb9477f621483a0fff4

commit 2e005aad2b9b4253e6d39cb9477f621483a0fff4
Author: Ken Rockot <rockot@chromium.org>
Date: Tue Sep 11 22:18:33 2018

[cloud-print] Fix service utility process launch

Fixes a bug which breaks sandboxed service utility process launching.
The launcher was invalidating the child process's Mojo channel handle
before launch.

TBR=rockot@chromium.org

(cherry picked from commit 2d480872f3afcc022749c86636b1a28acbe307f5)

Bug:  882158 
Change-Id: I406bc3adcf9be2e74dda87f536151b4f05ac3319
Reviewed-on: https://chromium-review.googlesource.com/1220266
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#590401}
Reviewed-on: https://chromium-review.googlesource.com/1220700
Reviewed-by: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3538@{#301}
Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811}
[modify] https://crrev.com/2e005aad2b9b4253e6d39cb9477f621483a0fff4/chrome/service/service_utility_process_host.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3cb1c06f365013020f5b23278815716e322b8900

commit 3cb1c06f365013020f5b23278815716e322b8900
Author: Ken Rockot <rockot@chromium.org>
Date: Tue Sep 11 22:18:20 2018

[cloud-print] Fix service utility process launch

Fixes a bug which breaks sandboxed service utility process launching.
The launcher was invalidating the child process's Mojo channel handle
before launch.

TBR=rockot@chromium.org

(cherry picked from commit 2d480872f3afcc022749c86636b1a28acbe307f5)

Bug:  882158 
Change-Id: I406bc3adcf9be2e74dda87f536151b4f05ac3319
Reviewed-on: https://chromium-review.googlesource.com/1220266
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#590401}
Reviewed-on: https://chromium-review.googlesource.com/1220699
Reviewed-by: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3497@{#928}
Cr-Branched-From: 271eaf50594eb818c9295dc78d364aea18c82ea8-refs/heads/master@{#576753}
[modify] https://crrev.com/3cb1c06f365013020f5b23278815716e322b8900/chrome/service/service_utility_process_host.cc

What is the upgrade path for those of us affected by this issue?
Do we switch to the either the Stable/Beta/Dev/Canary builds on our production server?

Thanks!

The NextAction date has arrived: 2018-09-12

Verified the fix on Windows-10 using Chrome versions #70.0.3538.16 and #71.0.3550.0 as per the comment#13.
Attaching screen shot for reference.
Note: Couldn't verify the fix on Mac 10.13.1 and Ubuntu 14.04 as we are not getting any pop-up.
Observed the status as Printed on windows 10
Hence, the fix is working as expected. 
Note: Able to reproduce the issue on chrome version with out fix.

Could some one help us in verifying the fix on Mac and Linux as we couldn't get any pop-up.

Thanks...!!

Deleted: 882158 CL.PNG 301 KB

	882158 CL.PNG 301 KB View Download

re: Comment 27

This issue is affecting deployments of Cloud Print Connector as well, whether it's the CPC code that's broken or not. Users still have to use Chrome to print, so whether they are using the Cloud Print Service installed on their local server, or a printer available through a remote CPC server, the jobs are still hanging "in progress" if their Chrome client is v 69.

This bug is definitely only relevant to cloud print proxy, and has no
relevance to Chrome printing in general (via CPC or otherwise).

If you have a problem with general printing or CPC behavior, please file a
separate bug with details on reproducing the issue.

+ georgesak@, imranal@ and robertshield@ as FYI

I installed version 68 provided by Google support on our print server running 2012 r2  and after I registered the GCP connector and selected the printers I wanted to deploy I tried to go into Google admin and Chrome locked up and there were 11 Chrome processes running for the one tab.

hi

help

+privard@ FYI

posthumously bumping this to P1 status as this continues to severly impact customers until .94 is released.

Can someone provide a date that this fix will be pushed? Or explanation on how to install the temp fix?

Thank you,

Here is what I did:

Uninstalled chrome on the device where the printer(s) are connected.

Installed version 68 of the chrome browser.
Got it from here
https://www.slimjet.com/chrome/google-chrome-old-version.php
not sure that is the best place, but it worked.

After install went into services.msc and disabled Google Update Service (gupdate) and (gupdatem)

Opened chrome, added printers, shared them, back to printing as normal.
At least that is what I did.

current understanding is that issue occurs on Windows only. Marking accordingly.

Also requesting a postmortem for this, pls see go/chrome-postmortems for more details.

re-opening until we get this push and moving to P0 as this should block any further pushing of 69.

What Comment 49 suggested worked, thank you so much!!!

thank you

I've got dozens of printers shared among several hundred people. I can't uninstall Chrome 69 and go back which would force me to set all that up again and send out new links to everyone. So cloud printing for my site is down until this fix gets to stable release, because I am not going to switch to beta or dev. Needless to stay I'm stalking the chromereleases blog.
As for the suggestion to use the GCP Service/Connector instead, that hasn't been updated by Google in 8 years (at least for Windows). Problems with it are why I started using Chrome instead.
Once this is fixed I will likely be disabling update services and setting up test shared printers on a different machine so I can ensure it works right before allowing the upgrade.
The developers of Chrome need to understand these issues that users like me face.

@dthatc... comment 55
I agree with most everything you've said... however, you're incorrect about the Google Cloud Print Connector. It is somewhat regularly updated and the last update was April 2018. https://github.com/google/cloud-print-connector/releases

Ah see I was going here: https://tools.google.com/dlpage/cloudprintservice
I guess that link should not be used any longer. Thanks for the tip!

G Suite and Chrome Enterprise customers impacted by this issue can request Chrome 68 MSIs by submitting a support ticket, please reference internal issue 115725344 when submitting your ticket.

Any update on when and if this fix will be released with 69 or if we will need to wait for 70?

The current plan is to release a new 69 build with the fix early to mid next week once it's completed our full testing process.

 Issue 884092  has been merged into this issue.

Verified the fix on Windows-10 using Chrome versions #69.0.3497.100 as per the comment#13.
Attaching screen shot for reference.
Observed the status as Printed on windows 10
Hence, the fix is working as expected. 
Adding the Verified labels.
Note: Able to reproduce the issue on chrome version with out fix.

Thanks!

Deleted: 882158 100.PNG 426 KB

	882158 100.PNG 426 KB View Download

This issue also affects Chrome on chromebooks and Mac OS. It is not limited to Windows, as some have stated.

If you are having issues with Chromebooks or Mac OS, you are having a different issue. This bug is most definitely a Windows-only bug.

69.0.3497.100 is now pushing with the fix, please upgrade and restart cloud print 

69.0.3497.100 Works beautifully!! Thank you!

Confirmed fixed - printing with classic cloudprint printers on Windows works again with latest stable release of Chrome #69.0.3497.100

This remains an issue in Chrome OS (I realize it may not be the same issue,
but Cloud Print has not been working in Chrome OS # 68.0.3440.118 for over
a week.  I just checked and am not seeing a new update for Chrome OS yet.
I'm still hoping that the new update will restore Cloud Print to our
chromebooks!  In the meantime, I had to manually add our school printers as
CUPS printers to each and every teacher's computer (and our students just
can't print at the moment, because my time is too limited to do all of them)

- Valerie, in NC

Director of Communications
www.redeemerschool.org

If you are having printing issues on Chrome OS or Mac, please file separate bug reports with details on exactly what isn't working and how it can be reproduced.

This bug is a Windows-only bug with a Windows-only fix that has already been verified and is in the process of being rolled out.

Folks, can we re-close this bug yet?

For comment 68, if the Chromebooks send print jobs to a Windows print server, it is the print server that needs to have its Chrome updated, not the Chromebooks.

This was the thread that was sent to me in a link from the Google Chrome
help desk folks, accessed through our school's Google for Education admin
console.  If there is a different thread I should be monitoring or sending
comments on, please send it my way.

Regarding this comment... "For comment 68, if the Chromebooks send print
jobs to a Windows print server, it is the print server that needs to have
its Chrome updated, not the Chromebooks."... I would love elaboration on
how to achieve this. We have cloud print ready printers. No one has ever
set up a "Windows print server" here specifically to make the Chromebooks
work to print. And the Chrome help desk folks did not mention this as a
recommendation?!?!

Thanks.
Valerie

Director of Communications
www.redeemerschool.org

Restricting comments as the issue is fixed and verified. Please do reach out on your support case for step by step help. Thanks all.

Can this be marked as fixed now?