From: Paul Wachendorf <pwachend@uni-koeln.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcitool scan returns wrong bdaddr
Date: Mon, 26 Nov 2007 19:31:38 +0100 [thread overview]
Message-ID: <474B110A.7000804@uni-koeln.de> (raw)
In-Reply-To: <1196080043.17196.4.camel@aeonflux>
Hi Marcel,
I found the 3.21 tarball, thanks. Unfortunately the error still occurs
with the resulting libbluetooth.so.2.9.1. Because of the output from
ldd, I'm sure that hcitool is linked against the "right" lib. So the Bug
must be in 3.21 too, or there is an completely different Problem as I
assume, because of the same behavior with libbluetooth.so.2.9.0 from
debian lenny, and because you told me that it should work with an D-Bus
API, which is installed.
So perhaps the Problem is rooted in my D-Bus setup. I installed it from
the debian repository and thought it should work without any further
configurations.
I'll search for it,
thank you very much for your time and help,
Regards,
Paul
-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-11-26 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 19:35 [Bluez-users] hcitool scan returns wrong bdaddr Paul Wachendorf
2007-11-25 22:44 ` Paul Wachendorf
2007-11-26 5:38 ` Marcel Holtmann
2007-11-26 10:47 ` Paul Wachendorf
2007-11-26 12:27 ` Marcel Holtmann
2007-11-26 18:31 ` Paul Wachendorf [this message]
2007-11-29 7:43 ` Dave Young
2007-11-29 20:19 ` Marcel Holtmann
2007-11-30 2:52 ` Dave Young
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=474B110A.7000804@uni-koeln.de \
--to=pwachend@uni-koeln.de \
--cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).