Bug#743455: cups: Pause after backend failure (printer off) not reset by reboot
severity 743455 wishlist
merge 631025 743455
thanks
On Thu 13 Nov 2014 at 21:44:02 +0100, Jürgen Pfennig wrote:
> Dear Maintainer
>
> as I found out meanwhile the problem is related to the default cups error
> policy, which is "stop-printer".
>
> This state survives a reboot and may cause a lot of trouble to unexperienced
> users.
>
> In my country electricity is expensive and people usually turn off unneeded
> devices. If some users sends a job to such a printer cups enters the "stop-
> printer" state by default and the user might get very confused. To me this is
> a serious usability problem.
>
> Please make the "stop-printer" state local to a cups daemon session or change
> the default to "abort-job".
>
> Please feel free the close this bug if you want.
No need to; it is a valid wish and very close to what is in #631025.
Hence merging.
Regards,
Brian.
Reply to: