Bug 3924

Summary:	pythons-dbus: asynchronous method call errors broken
Product:	dbus	Reporter:	Lennart Poettering <mzsqb>
Component:	core	Assignee:	Havoc Pennington <hp>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	high
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

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.