Honor NO_REPLY on service-side

Submitted by Daniel Wagner

Assigned to Simon McVittie

Link to original bug (#32529)

Description

Hi,

The dbus pyhton binding I'm using, sends always a reply. In the setup I'm using this results into following syslog message:

Dec 20 18:31:29 candlejack dbus: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.125" (uid=500 pid=8472 comm="/usr/bin/python) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.91" (uid=0 pid=5240 comm="./connmand))

It would be very cool if the binding would honor the NO_REPLY flag. E.g. in ConnMan we do following on the server side:

dbus_message_set_no_reply(message, TRUE);

The client looks like this:

@dbus.service.method("net.connman.Counter",
			in_signature='oa{sv}a{sv}')
def Usage(self, path, home, roaming):
	# do something
	return None

I was trying to figure out how the binding is handling NO_REPLY but I couldn't find a spot where this is handled. So if this is really missing, it would be nice to have NO_REPLY honored. Thanks!

btw: I'm using dbus-python-0.83.0-7.fc14.x86_64