Bug 744715 - Timeout for cups-driverd too short
Summary: Timeout for cups-driverd too short
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-10 09:50 UTC by Tim Waugh
Modified: 2011-10-19 04:42 UTC (History)
2 users (show)

Fixed In Version: cups-1.5.0-16.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-19 04:42:52 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tim Waugh 2011-10-10 09:50:59 UTC 
Description of problem:
When fetching a list of drivers while, say, a system backup is running, I frequently see timeouts.  It looks like cupsd is killing the cups-driverd process rather than relying on the timeout in cups-driverd itself.

Version-Release number of selected component (if applicable):
cups-1.5.0-15.fc16.x86_64
Comment 1 Tim Waugh 2011-10-11 13:07:45 UTC 
Turns out it's on the client end (libcups).
Comment 2 Fedora Update System 2011-10-11 13:10:45 UTC 
cups-1.5.0-16.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/FEDORA-2011-13168
Comment 3 Fedora Update System 2011-10-12 16:49:13 UTC 
Package cups-1.5.0-16.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing cups-1.5.0-16.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-13168
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2011-10-19 04:42:52 UTC 
cups-1.5.0-16.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.