Parent: 1f2e03bc5262e412e822dec7c17a783c487c18cb
Author: Philip Withnall <philip.withnall@collabora.co.uk>
Committer: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2015-12-04 14:28:32
Tree: cfe3ca1eec431e401120f4e501c7f165f31adb33
gdbus: Drop message replies if the sender requested no reply If the sender flags a D-Bus message as not expecting a reply, it is against system bus policy to send a reply — sending one will result in errors being sent to us by dbus-daemon. Magically drop all replies to messages which request no reply. ofonod is one process which sends BlueZ messages which request no reply, when it is setting up a hands-free agent. This is not a complete fix. In an ideal world, the existing check for G_DBUS_METHOD_FLAG_NOREPLY would be dropped, as the server should be prepared to return a reply to every method, if the client requests and expects one — otherwise the client will time out. However, that’s a much bigger change with a much bigger risk of breaking things, so I’ll stick with this for now.
Diffstat
| M | gdbus/object.c | | | 3 | ++- |
1 files changed, 2 insertions(+), 1 deletions(-)