From: Daniel Abraham <daniel.shrugged@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: no client session close in obexd 0.23?
Date: Tue, 27 Apr 2010 02:37:03 +0300 [thread overview]
Message-ID: <h2s2c3916b71004261637le0d83946y724f6ddb538c093@mail.gmail.com> (raw)
In-Reply-To: <g2s2d5a2c101004261124lcd36410dhbfe959945f0aa5a9@mail.gmail.com>
Thanks!
Followup question - I'm trying to use it, but it throws this exception:
dbus.exceptions.DBusException: org.openobex.Error.InvalidArguments:
What am I doing wrong? What is the right input?
Here's a sample Python script:
---
#!/usr/bin/env python
import dbus
bus = dbus.SessionBus()
proxy = bus.get_object('org.openobex.client', '/')
client = dbus.Interface(proxy, 'org.openobex.Client')
address = '00:1C:26:FC:15:AF'
print('Opening FTP session')
path = client.CreateSession({'Target': 'ftp', 'Destination': address})
print(path)
client.RemoveSession(path)
print('FTP session closed')
---
Output:
Opening FTP session
/org/openobex/session0
Traceback (most recent call last):
File "./test-ftp.py", line 14, in <module>
client.RemoveSession(path)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line
630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.openobex.Error.InvalidArguments:
next prev parent reply other threads:[~2010-04-26 23:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 9:29 no client session close in obexd 0.23? Daniel Abraham
2010-04-26 10:39 ` Daniel Abraham
2010-04-26 18:24 ` Luiz Augusto von Dentz
2010-04-26 23:37 ` Daniel Abraham [this message]
2010-04-27 7:10 ` Luiz Augusto von Dentz
2010-04-27 10:35 ` Daniel Abraham
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=h2s2c3916b71004261637le0d83946y724f6ddb538c093@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).