[cups.bugs] [HIGH] STR #2341: STATE:paused handling by scheduler

[Dmitry Sharov]

DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

According to http://www.cups.org/str.php?L1903
'paused' state reported by filter/backend should stop job
along with a queue and retain printer-state-message
to be the last message reported by the filter chain.

Contrary to that specification after STATE:paused is reported by
filter chain scheduler does not explictly stop current job by
sending a TERM signal to the filter chain.

Also the following can be observed after STATE:paused is reported:
- If the entire filter chain exits with 0 exit status,
job is dismissed from the print queue job list as completed
and printer-state-message is cleared, also print queue is
resumed implicitly;
- If at least one filter in the filter chain exits with non-zero
status then job is stopped but contents of printer-state-message
is replaced with ' failed', print queue retains stopped state.

In both cases printer-state-message is not preserved as it should.

Link: http://www.cups.org/str.php?L2341
Version: 1.3-current