From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] pin code
Date: Sun, 04 Mar 2007 18:36:50 +0100 [thread overview]
Message-ID: <1173029811.5752.11.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <BAY117-F18EFD8ECC30C22E9C1FE4ABF870@phx.gbl>
Hi Kelvin,
> i am faced with the sam problems as KS H. I have also cross compiled dBus
> and Bluez Util for ARM using Scratchbox.
> I followed the similar steps provided by Prabhu. However, I do not have the
> message.pid entry in /var/run but have an additional "pid" entry in
> /var/run/dbus.
>
> And when i try to execute hcid i received the following error:
> # hcid -n -f /etc/bluetooth/hcid.conf
> hcid[790]: Bluetooth HCI daemon
> hcid[790]: Can't open system message bus connection: Failed to connect to
> socket /var/run/dbus/system_bus_socket: Connection refused
> hcid[790]: Unable to get on D-Bus
>
> Please advice. Thank you
this can mean two things. Either the system bus is not running or the
security settings for hcid to claim the org.bluez namespace are not
correctly set.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-03-04 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 11:43 [Bluez-users] Re: pin code Kelvin Xu
2007-03-04 17:36 ` Marcel Holtmann [this message]
2007-03-04 17:28 ` [Bluez-users] " Kelvin Xu
2007-03-09 9:27 ` Kelvin Xu
-- strict thread matches above, loose matches on Subject: below --
2007-01-23 13:46 KS H
2007-01-26 5:45 ` Prabhu nath
2007-12-17 9:10 ` Sumeet VERMA
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=1173029811.5752.11.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--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