Bug 507572 - CUPS backend exits with status 1
Summary: CUPS backend exits with status 1
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-23 11:03 UTC by Tim Waugh
Modified: 2010-06-28 13:14 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-28 13:14:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tim Waugh 2009-06-23 11:03:10 UTC
Description of problem:
I get a lot of bluez-cups pollution in the CUPS error_log file:

E [23/Jun/2009:11:58:39 +0100] [cups-deviced] PID 20097 (bluetooth) stopped with status 1!

There's no need for it; just exit with status 0 when there are no devices.

Version-Release number of selected component (if applicable):
bluez-4.37-2.fc11.x86_64

Comment 1 Bastien Nocera 2009-06-24 14:37:24 UTC
Does this build fix it for you?
http://koji.fedoraproject.org/koji/taskinfo?taskID=1433635

Comment 2 Tim Waugh 2009-06-24 14:41:20 UTC
Yes, fixed.  Thanks.

Comment 3 Fedora Update System 2009-06-24 14:52:17 UTC
bluez-4.37-4.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/bluez-4.37-4.fc11

Comment 4 Fedora Update System 2009-06-27 02:41:25 UTC
bluez-4.37-4.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update bluez'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-6954

Comment 5 Fedora Update System 2009-06-30 21:35:10 UTC
bluez-4.42-1.fc11, gnome-bluetooth-2.27.7.1-1.fc11, gnome-phone-manager-0.65-2.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update bluez gnome-bluetooth gnome-phone-manager'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7140

Comment 6 Bug Zapper 2010-04-27 15:11:39 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2010-06-28 13:14:52 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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