Linux bluetooth development
 help / color / mirror / Atom feed
From: "thHog" <bluez@t3i.nl>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] python / dbus issue
Date: Fri, 23 Nov 2007 03:22:46 +0100	[thread overview]
Message-ID: <E1IvOBq-0005p1-0g@daffy.sipo.nl> (raw)

Hi,

I tried my first python script for accessing bluez through dbus. The bluez
setup is complete and I can scan and connect bluetooth devices using hcitool
and rfcomm tools. The dbus setup is working as well, the "dbus-monitor
--system" shows bluez messages when starting bluez.

But, I tried to run the following python script (and several other examples
from the internet):


import dbus
bus = dbus.SystemBus();
obj = bus.get_object('org.bluez', '/org/bluez')
manager = dbus.Interface(obj, 'org.bluez.Manager')
print manager.ListAdapters()


The output from this script is:

Traceback (most recent call last):
  File "./mydbus.py", line 27, in ?
    print manager.ListAdapters()
  File "/usr/lib/python2.4/site-packages/dbus/proxies.py", line 85, in
__call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.4/site-packages/dbus/proxies.py", line 169, in
__call__
    reply_message =
self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method
"ListAdapters" with signature "" on interface "org.bluez.Manager" doesn't
exist

On starting /etc/init.d/bluetooth, dbus-monitor --system shows:

$ dbus-monitor --system
signal sender=org.freedesktop.DBus -> dest=:1.5 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.5"
signal sender=org.freedesktop.DBus -> dest=(null destination)
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameOwnerChanged
   string ":1.6"
   string ""
   string ":1.6"
signal sender=org.freedesktop.DBus -> dest=(null destination)
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameOwnerChanged
   string "org.bluez"
   string ""
   string ":1.6"
signal sender=:1.6 -> dest=(null destination) path=/org/bluez/Manager;
interface=org.bluez.Manager; member=DeviceAdded
   string "/org/bluez/Device/hci0"
signal sender=:1.6 -> dest=(null destination) path=/org/bluez/Device/hci0;
interface=org.bluez.Device; member=Up
signal sender=:1.6 -> dest=(null destination) path=/org/bluez/Device/hci0;
interface=org.bluez.Device; member=PropertyChanged
   string "name"
   string ""

What is wrong here?

Thanks,
--theHog



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2007-11-23  2:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  2:22 thHog [this message]
2007-11-23 12:12 ` [Bluez-devel] python / dbus issue Manuel Naranjo
  -- strict thread matches above, loose matches on Subject: below --
2007-11-23 20:17 thHog

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=E1IvOBq-0005p1-0g@daffy.sipo.nl \
    --to=bluez@t3i.nl \
    --cc=bluez-devel@lists.sourceforge.net \
    /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