Hi, 
could you please help triage this issue ?

I took a look through the logs and it looks like everything completed as expected.  I'm surprised that printing the PDF works.  We're aware of an issue where some documents result in really large PS crbug.com/745857.  This could be related but more investigation would be necessary to confirm.

Skau@
The customer has provided some extra confirmations listed below.

-Upgraded to M60 from M59 but could not resolved the issue.

---From Print Preview Window---
-select "all" > print : Failed.
-select "all" > select "# of pages"(example 1- 10) >select back to "All" >print :Failed.
---Extra info---
- The customer has confirmed that other Chrome Device model (ASUS C302) is printing without issue.
- They have provided fresh device log files from both devices and I saved it below linked drive site.
(Date and Time logs has been collected: 09/09/2017 11:30am JST )
https://drive.google.com/open?id=0B01YYztUbOCuTm1oNmlDclFRaUE

Please let me know if you need extra confirmation or log files from the customer site.

We are following crbug.com/745857 as well, but there is no update since Aug 21 so please update it as well.

From logs, device is a peppy.

Looks like PDF to PS conversion is taking exceptionally long, greater than 20 seconds, and we're giving up on the job and marking it as cancelled.  I'll try to find a peppy to see if I can reproduce this.

skau@,
any updates for this issue? Customer is requesting an update

I just checked this on peppy and it seems to be working.
Chrome: 63.0.3219.0
Platform: 9934.0

I can use the linked PPD to print to a PostScript printer that we have in the office.  We can also see timeouts like this if the printer is unreachable from the chromebook.  Is the customer using the same configuration on both devices?

@skomiya, can you add details once you get the info from customer? Thanks.

 skau@
Let me ask you some questions about your previous reproducing test for this issue.
1. Were you able to reproduce the same issue?
2. Could you please confirm by CYAN device?
3. Have you confirmed for other OS versions? Is there any change since M63?
4. Please explain about which configuration you are talking about.
5. Is there any configuration that can be extend the time out? 


I am going to ask them about the configuration on both devices but I believe they are using the same config.

1. I was not able to reproduce the issue.
2. I'll see if I can find a CYAN and report back.
3. I'll double check the behavior in M61.
4. Are the network configurations and printers configured the same on both devices?
5. Timeout is not configurable.


Do we know the make and model of the printer? The printer could be behaving in a way that we haven't anticipated.

-Affected Printer Model: RICOH MP C3503 and other RICOH models.
-Printer Driver: Ricoh-Basic_PS_Color.ppd
Also, both affected (R11/CYAN) and non affected (C302CA/cave)devices are using the same network configuration.

Ah.  You're supplying your own PPD.  On the CYAN, can you try to edit the printer configuration and choose the PPD again to see if that works?

I requested the customer, so I will update you once got the result from them.
They have also tested by 61.0.3163.123 but still the same.

skau@
The customer provided a new device log after recreating the CUPS printer settings and upgrading the OS to M62, but the problem still remains.

Please refer the provided new device log from the customer(Model Acer Chromebook R11 (CB5-132T / C738T)).
https://drive.google.com/open?id=150eQ60dmnzYel_boyaMk4UD8BOGFgQTw

Model	Acer Chromebook R11 (CB5-132T / C738T)
Google Chrome Version	62.0.3202.82
Platform Version	9901.66.0 (Official Build) stable-channel cyan
Firmware Version	Google_Cyan.7287.57.125


Model	Acer Chromebook R11 (CB5-132T / C738T)
2017-11-12T15:22:25.240759+09:00 INFO cupsd[4747]: REQUEST localhost - - "POST /printers/578340d9-0fa2-4739-9310-6a16d22dff4e HTTP/1.1" 200 199 Close-Job successful-ok
2017-11-12T15:22:27.571810+09:00 NOTICE cupsd[4747]: [Job 1] PID 2 (/usr/libexec/cups/filter/pdftopdf) exited with no errors.
2017-11-12T15:22:46.109606+09:00 INFO cupsd[4747]: REQUEST localhost - - "POST /jobs/ HTTP/1.1" 200 203 Cancel-Job successful-ok
2017-11-12T15:22:46.112208+09:00 NOTICE cupsd[4747]: [Job 1] PID 5 (/usr/libexec/cups/backend/lpd) exited with no errors.
2017-11-12T15:22:46.114313+09:00 NOTICE cupsd[4747]: [Job 1] PID 4 (/usr/libexec/cups/filter/foomatic-rip) exited with no errors.
2017-11-12T15:22:46.129904+09:00 NOTICE cupsd[4747]: [Job 1] PID 3 (/usr/libexec/cups/filter/pdftops) exited with no errors.


———————

Asus C302CA device that is working OK log from previous thread #4 
https://drive.google.com/open?id=0B01YYztUbOCuRWs3QVh6VzhNMFE

2017-09-09T11:18:08.443029+09:00 INFO cupsd[7286]: REQUEST localhost - - "POST /printers/96d6d63b-6046-48e8-8ada-b33e17b0ae2f HTTP/1.1" 200 199 Close-Job successful-ok
2017-09-09T11:18:09.308853+09:00 NOTICE cupsd[7286]: [Job 1] PID 2 (/usr/libexec/cups/filter/pdftopdf) exited with no errors.
2017-09-09T11:18:19.515610+09:00 NOTICE cupsd[7286]: [Job 1] PID 3 (/usr/libexec/cups/filter/pdftops) exited with no errors.
2017-09-09T11:18:19.524163+09:00 NOTICE cupsd[7286]: [Job 1] PID 4 (/usr/libexec/cups/filter/foomatic-rip) exited with no errors.
2017-09-09T11:18:32.444553+09:00 DEBUG kernel: [35776.458414] SELinux: initialized (dev proc, type proc), uses genfs_contexts
2017-09-09T11:18:34.330550+09:00 DEBUG kernel: [35778.344696] SELinux: initialized (dev proc, type proc), uses genfs_contexts
2017-09-09T11:19:34.056892+09:00 NOTICE cupsd[7286]: [Job 1] PID 5 (/usr/libexec/cups/backend/lpd) exited with no errors.

Please let me know if you require any other info from the customer side.

Upon closer inspection of the logs, and some testing with my peppy, this is definitely a timeout issue where that particular document takes greater than 20 seconds to render and we kill the job prematurely.  I'll file a separate bug to track.

skau@
Thanks for your support and update.
I will follow  crbug.com/786182  as well.