Red Hat Bugzilla – Bug 435081
Bad CUPS backend behaviour when device absent
Last modified: 2008-03-14 13:09:46 EDT
Description of problem:
If the target device is absent when a print job is processed, the bluetooth CUPS
backend just fails with exit code 1. This will cause the queue's error-policy
to be invoked, which defaults to disabling the queue.
It would be better for the backend to keep retrying (say, every 60s) until it
Version-Release number of selected component (if applicable):
What happens for other backends when a device is temporarily absent (a USB
printer is unplugged, or a network printer is unreachable)?
The CUPS backends for USB and socket sleep 30s and retry. See
Fixed upstream as well.