Description of problem: Dbus-send unable to send dict arguments. Version-Release number of selected component (if applicable): dbus-1.1.2-12.el5 How reproducible: 100% Steps to Reproduce: 1. Send: dbus-send --dest=org.freedesktop.ExampleName /org/freedesktop/sample/object/name org.freedesktop.ExampleInterface.ExampleMethod dict:string:int32:"one",1 Actual results: process 21869: arguments to dbus_message_iter_open_container() were incorrect, assertion "(type == DBUS_TYPE_STRUCT && contained_signature == NULL) || (type == DBUS_TYPE_DICT_ENTRY && contained_signature == NULL) || (type == DBUS_TYPE_VARIANT && contained_signature != NULL) || (type == DBUS_TYPE_ARRAY && contained_signature != NULL)" failed in file dbus-message.c line 2356. This is normally a bug in some application using the D-Bus library. process 21869: dbus message iterator looks uninitialized or corrupted process 21869: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_message_iter_append_check (real)" failed in file dbus-message.c line 2239. This is normally a bug in some application using the D-Bus library. process 21869: dbus message iterator looks uninitialized or corrupted process 21869: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_message_iter_append_check (real)" failed in file dbus-message.c line 2239. This is normally a bug in some application using the D-Bus library. process 21869: dbus message iterator looks uninitialized or corrupted process 21869: arguments to dbus_message_iter_close_container() were incorrect, assertion "_dbus_message_iter_append_check (real_sub)" failed in file dbus-message.c line 2414. This is normally a bug in some application using the D-Bus library. Expected results: No output, message should be send. Additional info:
*** Bug 472044 has been marked as a duplicate of this bug. ***
process 7970: arguments to dbus_message_iter_open_container() were incorrect, assertion "(type == DBUS_TYPE_STRUCT && contained_signature == NULL) || (type == DBUS_TYPE_DICT_ENTRY && contained_signature == NULL) || (type == DBUS_TYPE_VARIANT && contained_signature != NULL) || (type == DBUS_TYPE_ARRAY && contained_signature != NULL)" failed in file dbus-message.c line 2356. This is normally a bug in some application using the D-Bus library. Segmentation fault throwable also with dbus-python, see: https://bugzilla.redhat.com/show_bug.cgi?id=469151#c1 https://bugzilla.redhat.com/attachment.cgi?id=321903 [note] For reproduce uncomment commentd lines in example-client.py. So now we have three ways to verify this bug.
hmm, is there an upstream commit we can easily backport for this one?
Not a regression, work fine on RHEL5.2 U2 (dbus-1.0.0-7.el5)
From David Z: "If this is just a bug in dbus-send(1) I'm not sure it's worth fixing for RHEL5 unless some customer jumps on it; most people don't use dbus-send(1), the ones that do rarely use it for dicts. Also, comment 5 seems to indicate this is fine for 5.2 and up (though the comment is a bit ambiguous). I'm pretty sure this is not a bug in libdbus; otherwise HAL, NM wouldn't work and then you would know soon enough. Suggest to close the bug." Concur on that -- I'd be surprised if dbus couldn't send dicts. Closing.