Bug 3924 - pythons-dbus: asynchronous method call errors broken
Summary: pythons-dbus: asynchronous method call errors broken
Status: RESOLVED FIXED
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-31 04:33 UTC by Lennart Poettering
Modified: 2006-08-01 10:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Lennart Poettering 2005-07-31 04:33:33 UTC
Consider  a server replying to a method call with an error message generated
like this:

  reply = dbus_message_new_error(i->message,
"org.freedesktop.Avahi.TimeoutError", NULL);

(i.e. error_message is NULL (!))

If a python-dbus based client issued this method call asynchronously, the
specified error function ist not called. Instead "Exception
exceptions.IndexError: 'list index out of range' in
'dbus_bindings._pending_call_notification' ignored
" is printed. If the error_message on the server side is non-NULL the error is
delivered correctly. If the method call is executed synchronously the error is
delivered correctly, regardless of error_message.
Comment 1 John (J5) Palmieri 2005-08-17 10:19:03 UTC
Fixed in bothe the glib and python bindings


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.