Bug 435081 - Bad CUPS backend behaviour when device absent
Bad CUPS backend behaviour when device absent
Product: Fedora
Classification: Fedora
Component: bluez-utils (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Woodhouse
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-02-27 04:17 EST by Tim Waugh
Modified: 2008-03-14 13:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-14 13:09:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2008-02-27 04:17:49 EST
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):
Comment 1 David Woodhouse 2008-02-27 15:59:45 EST
What happens for other backends when a device is temporarily absent (a USB
printer is unplugged, or a network printer is unreachable)? 
Comment 2 Tim Waugh 2008-02-27 17:22:58 EST
The CUPS backends for USB and socket sleep 30s and retry.  See
Comment 3 Bastien Nocera 2008-03-14 13:09:46 EDT
Fixed upstream as well.

Note You need to log in before you can comment on or make changes to this bug.