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 succeeds. Version-Release number of selected component (if applicable): 3.20-6.fc8
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 cups-1.3.6/backend/*.c.
Fixed upstream as well.