Parent: a43e6512ccc74fd5f01ce63c11bfc793ace5c894
Author: Christian Fetzer <christian.fetzer@bmw-carit.de>
Committer: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2013-05-24 00:34:31
Tree: 6030f72662121870070b44510268ce94038c85c9
obexd: Fix SetPath response This fixes the issue, that failed attempts to the OBEX SetPath command are not propagated through the D-Bus API. Trace: method call sender=:1.942 -> dest=:1.934 serial=8 path=/org/bluez/obex/client/session3; interface=org.bluez.obex.MessageAccess1; member=SetFolder string "test" method return sender=:1.934 -> dest=:1.942 reply_serial=8 method call sender=:1.946 -> dest=:1.945 serial=8 path=/org/bluez/obex/client/session0; interface=org.bluez.obex.MessageAccess1; member=SetFolder string "test" error sender=:1.945 -> dest=:1.946 error_name=org.bluez.obex.Error.Failed reply_serial=8 string "Not Found"
Diffstat
| M | obexd/client/session.c | | | 2 | +- |
1 files changed, 1 insertions(+), 1 deletions(-)