Created attachment 394902 [details] test.py Description of problem: When calling a D-Bus method asynchronously with parameters whose types do not match the method's signature (e.g. the service has changed the interface in an incompatible way), there is no way to catch the failure. Version-Release number of selected component (if applicable): dbus-python-0.83.0-6.fc12.x86_64 How reproducible: 100% Steps to Reproduce: 1.Install cups-pk-helper-0.0.4-10.fc12 2.Run the attached test.py Actual results: ERROR:dbus.connection:Unable to set arguments (0, 0, [], []) according to signature u'iss': <type 'exceptions.TypeError'>: Expected a string or unicode object Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 586, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 391, in _introspect_reply_handler self._introspect_execute_queue() File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 378, in _introspect_execute_queue proxy_method(*args, **keywords) File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 132, in __call__ **keywords) File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 566, in call_async message.append(signature=signature, *args) TypeError: Expected a string or unicode object ^CTraceback (most recent call last): File "/tmp/test.py", line 30, in <module> loop.run () KeyboardInterrupt Expected results: 'Got error', 'Got reply', or 'Got exception'.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
Still happens with dbus-python-0.83.0-7.fc14.x86_64.
*** Bug 743446 has been marked as a duplicate of this bug. ***
Created attachment 529522 [details] test.py Still fails with dbus-python-0.83.0-8.fc15.x86_64.
Note that in bug #743446 this same issue causes a hang when a D-Bus call simply times out (for some reason). This breaks the guarantees offered by the API. Setting priority/severity accordingly.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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
Still fails with dbus-python-0.83.0-9.fc17.x86_64.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Please try with https://admin.fedoraproject.org/updates/FEDORA-2013-3108/dbus-python-1.1.1-3.fc18 and reopen if you still have issues.
It crashes now. ERROR:dbus.connection:Unable to set arguments (0, 0, 0, []) according to signature u'iiasas': <type 'exceptions.TypeError'>: 'int' object is not iterable process 9848: arguments to dbus_message_get_destination() were incorrect, assertion "message != NULL" failed in file dbus-message.c line 3376. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Aborted (core dumped) In some ways I guess that's better than silently failing, but it's unexpected. Shouldn't calling a method with an incorrect signature give me an exception?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.