From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez-utils 3.36: Unable to get on D-Bus
Date: Thu, 17 Jul 2008 11:06:16 +0300 [thread overview]
Message-ID: <2A1E7937-4DA2-4B00-8EBD-10DC50269D54@gmail.com> (raw)
In-Reply-To: <e378cfb20807170101iec7c9e5jfeb3aa1afe9e01e@mail.gmail.com>
Hi,
On Jul 17, 2008, at 11:01, Nel D wrote:
> On Wed, Jul 16, 2008 at 9:04 PM, Voni Hakau <hakauvoni@gmail.com>
> wrote:
>>
>> I get the following error:
>>
>> # hcid -n -s -d
>> hcid[467]: Bluetooth HCI daemon
>> hcid[467]: Enabling debug information
>> hcid[467]: Unable to get on D-Bus
>
> Try starting hcid as root. Also check if another instance of "hcid" is
> already running when u issue this command??
Another common cause of this error is that the user hasn't installed
the D-Bus policy configuration for BlueZ into /etc/dbus-1/system.d
(the hcid/bluetooth.conf file).
Johan
-------------------------------------------------------------------------
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=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-07-17 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 15:34 [Bluez-users] bluez-utils 3.36: Unable to get on D-Bus Voni Hakau
2008-07-16 21:03 ` David Stockwell
2008-07-17 8:01 ` Nel D
2008-07-17 8:06 ` Johan Hedberg [this message]
2008-07-17 8:17 ` Voni Hakau
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=2A1E7937-4DA2-4B00-8EBD-10DC50269D54@gmail.com \
--to=johan.hedberg@gmail.com \
--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