public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heston James - Cold Beans" <heston.james@coldbeans.co.uk>
To: "'BlueZ development'" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] BlueZ not responding to dbus
Date: Sun, 27 Jul 2008 10:51:35 +0100	[thread overview]
Message-ID: <003a01c8efce$6103a770$230af650$@james@coldbeans.co.uk> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2076 bytes --]

Good morning guys,

 

I've tried discussing this on IRC over the past couple of days,
unfortunately my  net connection here is a little sketchy and I seem to drop
off the channel before I get chance to discuss it properly with anyone.

 

At the moment I can only describe the symptoms I've been seeing and with any
luck you'll be able to help me debug and diagnose the root cause of the
problem.

 

The problem seems to occur when performing an inquiry (periodic) when there
are many devices present, when performing the same operations during quieter
times in the office we don't seem to see this issue, however, when staff
here and in the neighbouring office turn up we start having problems.

 

Essentially it would seem that all other calls to the bluez dbus interfaces
results in the following error:

 

"DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken."

 

This is true for seemingly any calls I try to make, whether it be
GetAddress(), DefaultAdapter(),GetRemoteServiceHandles() or seemingly even
any of the operations invoked by obex-data-server.

 

Once I start to receive these errors, I kill my application and then try to
relaunch it and I receive:

 

"ERROR:dbus.proxies:Introspect error on :1.0:/org/bluez:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken."

 

Can anyone give me any idea as to whether this is normal behaviour? Or is
this due to me doing something wrong with the Bluetooth stack? I've been
testing this with BlueZ 3.36 on Kernel 2.6.25 and dbus 1.2 and I'm using the
BlueZ 3.x API.

 

I'd really appreciate any and all suggestions on this guys, I'm open to any
ideas J

 

Cheers.

 

Heston


[-- Attachment #1.2: Type: text/html, Size: 5102 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-07-27  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  9:51 Heston James - Cold Beans [this message]
2008-08-18  5:15 ` [Bluez-devel] BlueZ not responding to dbus Marcel Holtmann

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='003a01c8efce$6103a770$230af650$@james@coldbeans.co.uk' \
    --to=heston.james@coldbeans.co.uk \
    --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