Bug 741697 - [colord patch] DeleteDevice uses old colord API
Summary: [colord patch] DeleteDevice uses old colord API
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 16
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-27 15:53 UTC by Jiri Popelka
Modified: 2011-10-19 04:42 UTC (History)
3 users (show)

Fixed In Version: cups-1.5.0-16.fc16
Clone Of:
Environment:
Last Closed: 2011-10-19 04:42:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jiri Popelka 2011-09-27 15:53:36 UTC
I see this in error_log:
D Calling DeleteDevice(cups-Generic-PCL-6-PCL-XL)
D failed to DeleteDevice: org.freedesktop.DBus.Error.InvalidArgs:Type of message, `(s)', does not match expected type `(o)'


From colord Changelog:
commit a9d09602a722480a1872323ff54f3784cb63c926
Date:	2011-05-27
... This also changes the API of the DeleteProfile and DeleteDevice to use the object paths rather than profile and device IDs ...


The colordDeleteDevice() function in scheduler/colord.c should be probably fixed to call DeleteDevice method with object path of the device (e.g. /org/freedesktop/ColorManager/devices/cups_Generic_PCL_6_PCL_XL) instead of the device ID (e.g. cups-Generic-PCL-6-PCL-XL).


Version-Release number of selected component (if applicable):
cups-1.5.0-9.fc16

Comment 1 Richard Hughes 2011-10-03 11:07:02 UTC
I'll fix this now, thanks for the heads up.

Comment 2 Richard Hughes 2011-10-03 11:31:56 UTC
I'm just building cups-1:1.5.0-11.f17 with the fix:

Task info: http://koji.fedoraproject.org/koji/taskinfo?taskID=3398844

Comment 3 Tim Waugh 2011-10-04 10:01:06 UTC
Thanks.

Comment 4 Fedora Update System 2011-10-04 10:07:26 UTC
cups-1.5.0-11.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/FEDORA-2011-13168

Comment 5 Fedora Update System 2011-10-04 20:46:29 UTC
Package cups-1.5.0-13.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-13.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/cups-1.5.0-13.fc16
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2011-10-06 21:21:37 UTC
Package cups-1.5.0-14.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-14.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 7 Fedora Update System 2011-10-08 23:34:24 UTC
Package cups-1.5.0-15.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-15.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 8 Fedora Update System 2011-10-12 16:49:01 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 9 Fedora Update System 2011-10-19 04:42:38 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.