From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Daniel Abraham <daniel.shrugged@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: obexd OPP pull problem
Date: Tue, 27 Apr 2010 11:33:33 +0300 [thread overview]
Message-ID: <n2h2d5a2c101004270133xa4ea7dd5za238a58f9e67613@mail.gmail.com> (raw)
In-Reply-To: <g2l2d5a2c101004270020mb94d092cnef88b98b147beba0@mail.gmail.com>
Hi,
On Tue, Apr 27, 2010 at 10:20 AM, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> Hi,
>
> On Tue, Apr 27, 2010 at 2:12 AM, Daniel Abraham
> <daniel.shrugged@gmail.com> wrote:
>> I'm trying to write a Python script that pulls a business card via OPP
>> (almost the same as the obexd test script "pull-business-card", except
>> it also handles pairing).
>>
>> My problem is that when I call the method "PullBusinessCard", it
>> returns almost immediately, withtout a D-Bus exception (i.e. should be
>> successful), but no output file can be found.
>>
>> Here's what I see in /var/log/messages:
>>
>> Apr 27 01:20:54 dabraham-mobl bluetoothd[1529]: link_key_request
>> (sba=00:21:86:7A:E7:67, dba=00:1C:26:FC:15:AF)
>> Apr 27 01:20:54 dabraham-mobl obex-client[3067]: Transfer(0xd4cb40)
>> Error: Method not allowed
>
> It should return a D-Bus error due to transfer error, which is why it
> doesn't complete the transfer, so it might be a bug in vcard pull
> logic, but why the transfer is failing I don't know it shouldn't
> matter if you are paring or not.
This should fix at least the D-Bus error:
http://gitorious.org/obexd/vudentzs-clone/commit/32e48446b6b8cd72e15988c673a60c7fb47b0862
--
Luiz Augusto von Dentz
Computer Engineer
next prev parent reply other threads:[~2010-04-27 8:33 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 [this message]
2010-04-27 11:51 ` Daniel Abraham
2010-05-12 21:21 ` Daniel Abraham
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=n2h2d5a2c101004270133xa4ea7dd5za238a58f9e67613@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=daniel.shrugged@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).