Bug 435081

Summary: Bad CUPS backend behaviour when device absent
Product: [Fedora] Fedora Reporter: Tim Waugh <twaugh>
Component: bluez-utilsAssignee: David Woodhouse <dwmw2>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 8CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-14 17:09:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tim Waugh 2008-02-27 09:17:49 UTC
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

Comment 1 David Woodhouse 2008-02-27 20:59:45 UTC
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 22:22:58 UTC
The CUPS backends for USB and socket sleep 30s and retry.  See
cups-1.3.6/backend/*.c.

Comment 3 Bastien Nocera 2008-03-14 17:09:46 UTC
Fixed upstream as well.