On Tue, Apr 27, 2010 at 2:51 PM, Daniel Abraham <daniel.shrugged@xxxxxxxxx> wrote: > On Tue, Apr 27, 2010 at 11:33 AM, Luiz Augusto von Dentz > <luiz.dentz@xxxxxxxxx> wrote: >> >> This should fix at least the D-Bus error: >> >> http://gitorious.org/obexd/vudentzs-clone/commit/32e48446b6b8cd72e15988c673a60c7fb47b0862 > > Actually, that's not what I see. I'm using the "pull-business-card" > script (which doesn't use any try-except block), and it doesn't crash > with an exception, even though "dbus-monitor --session" shows the > error (below). Is it lost somehow before it reaches Python's D-Bus > caller object? > > method call sender=:1.147 -> dest=:1.142 serial=4 path=/; > interface=org.openobex.Client; member=PullBusinessCard > array [ > dict entry( > string "Destination" > variant string "00:1C:26:FC:15:AF" > ) > ] > string "d.vcf" > method call sender=:1.142 -> dest=org.freedesktop.DBus serial=18 > path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; > member=AddMatch > string "type='signal',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0=':1.147'" > method return sender=:1.142 -> dest=:1.147 reply_serial=4 > error sender=:1.142 -> dest=:1.147 > error_name=org.openobex.Error.Failed reply_serial=4 > string "Method not allowed" > method call sender=:1.142 -> dest=org.freedesktop.DBus serial=21 > path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; > member=RemoveMatch > string "type='signal',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0=':1.147'" > signal sender=org.freedesktop.DBus -> dest=(null destination) > serial=10 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; > member=NameOwnerChanged > string ":1.147" > string ":1.147" > string "" I revisited the issue above, and a problem still reproduces, sorta... I use the following setup: Fedora 12, BlueZ 4.64, obexd 0.23 on both sides. And after a while "PullBusinessCard" started to work, i.e. I pull the default vcard (of 50 bytes) from 1 side to the other. But... Even though the HCI dump shows that the text passed through, the vCard file isn't found anywhere. Also, it looks as if there's some timing issue: 1. If I pull a 50-byte card, the remote computer recognize successful completion event 2. If I pull a 20-KB card, the remote computer doesn't recognize any completion event Either way, the local computer claims to be successful, even though there's no saved vcard file. Another thing I noticed is that the remote host from which I try to pull the vcard (also BlueZ 4.64 + obexd 0.23) writes this in "/var/log/messages": obexd[...] New connection from: <BD address>, channel <...> (and immediately, with the same timestamp:) obexd[...] obexd_handle_input: poll event HUP ERR I'm also attaching 2 hcidumps (saved on the local computer trying to do the pulling). Any idea how to work around these failures? Thanks
Attachment:
opp-pull-fail.hcidump
Description: Binary data
Attachment:
opp-pull-success.hcidump
Description: Binary data
