Handle error case where Printer IP is valid, but not hitting a printer |
|||
Issue descriptionIn the case where a user prints to a printer setup with an invalid IP, the current expected behavior is that the print job will timeout and provide an error notification. This is occurring if the IP is entirely invalid, but not getting identified when the IP is valid, but does not belong to the specified printer. We should also handle this case as an error and timeout.
,
Apr 14 2017
,
May 3 2017
Cannot reproduce. I double checked the CUPS code, and this error stems from the printer reporting that it's busy. In this case, we're correct to wait and retry the job as the printer is recoverable with some manual intervention. "The printer is busy" is found in the logs. |
|||
►
Sign in to add a comment |
|||
Comment 1 by skau@google.com
, Apr 14 2017