New issue
Advanced search Search tips

Issue 823520 link

Starred by 2 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Report connection timeout from CUPS

Project Member Reported by skau@chromium.org, Mar 19 2018

Issue description

With change https://chromium-review.googlesource.com/c/chromium/src/+/966795, the CUPS backend will timeout on it's own.  However, it won't tell us why the print job stopped (just that the backend failed).  Report the real failure in printer-state-reasons.
 

Comment 1 by skau@chromium.org, Mar 19 2018

Change was made in response to  crbug.com/786182 
Labels: -Pri-2 -M-68 M-70 Pri-0
Can we prioritize this for M70?  This is masking some configuration issues.
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 16

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -M-70 M-69
Labels: -Pri-0 Pri-1
Status: Started (was: Assigned)
I can confirm that we report a failure for the print job in this situation.  We just report the generic error message. This is not the cause of "infinitely hanging" print jobs.
Labels: -M-69 M-71
Bump! What's the status on this bug?
Cc: cupsmigration-core@google.com
 Issue 904859  has been merged into this issue.
Labels: -M-71 M-73

Sign in to add a comment