linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Abraham <daniel.shrugged@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: obexd OPP pull problem
Date: Thu, 13 May 2010 00:21:52 +0300	[thread overview]
Message-ID: <AANLkTikhFOl6UiI6BN5-xunik9w0FJwW_a7FMbm0-vq7@mail.gmail.com> (raw)
In-Reply-To: <q2z2c3916b71004270451r957e5befp631d413d4f316afe@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3003 bytes --]

On Tue, Apr 27, 2010 at 2:51 PM, Daniel Abraham
<daniel.shrugged@gmail.com> wrote:
> On Tue, Apr 27, 2010 at 11:33 AM, Luiz Augusto von Dentz
> <luiz.dentz@gmail.com> 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 #2: opp-pull-fail.hcidump --]
[-- Type: application/octet-stream, Size: 6616 bytes --]

[-- Attachment #3: opp-pull-success.hcidump --]
[-- Type: application/octet-stream, Size: 2533 bytes --]

  reply	other threads:[~2010-05-12 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 23:12 obexd OPP pull problem Daniel Abraham
2010-04-27  7:20 ` Luiz Augusto von Dentz
2010-04-27  8:33   ` Luiz Augusto von Dentz
2010-04-27 11:51     ` Daniel Abraham
2010-05-12 21:21       ` Daniel Abraham [this message]
2010-05-13  1:00         ` Vinicius Gomes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikhFOl6UiI6BN5-xunik9w0FJwW_a7FMbm0-vq7@mail.gmail.com \
    --to=daniel.shrugged@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).