Bug 5691 - Nearest should return CUPS_BACKEND_CANCEL instead of CUPS_BACKEND_OK on errors
Summary: Nearest should return CUPS_BACKEND_CANCEL instead of CUPS_BACKEND_OK on errors
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Printing (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Henrik Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-29 18:32 CET by Karl Mikaelsson
Modified: 2015-11-03 10:45 CET (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Karl Mikaelsson cendio 2015-10-29 18:32:28 CET 
When nearest hits errors like it can't find where it's supposed to print or similar, it returns CUPS_BACKEND_OK (0) but discards the job silently (from the perspective of the user). Trying to print the document again does not give you any hints on where the first job went.

If we instead would return CUPS_BACKEND_CANCEL on these types of errors, CUPS will indicate that the last printer job did not complete.

> # lpstat -t
> [...]
> printer nearest is idle.  enabled since Thu 29 Oct 2015 06:19:16 PM CET
> 	No near printers for terminal (52:54:00:D7:5C:66) in configuration! DELETING JOB
> [...]

CUPS_BACKEND_CANCEL is described as "The print file was not successfully transmitted because one or more attributes are not supported or the job was canceled at the printer. The scheduler will respond to this by canceling the job.". It's been present since at least CUPS 1.3 - can't find older documentation on cups.org.

We'd have to reconsider what information is safe to share to users through this channel though.
Note You need to log in before you can comment on or make changes to this bug.