Bug 435081 - Bad CUPS backend behaviour when device absent
Summary: Bad CUPS backend behaviour when device absent
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez-utils
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: David Woodhouse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-02-27 09:17 UTC by Tim Waugh
Modified: 2008-03-14 17:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-14 17:09:46 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.