public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nel D" <newatlinux@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Unable to get on D-Bus
Date: Tue, 19 Feb 2008 20:27:49 +0530	[thread overview]
Message-ID: <e378cfb20802190657m69936857ob676ad575842c222@mail.gmail.com> (raw)
In-Reply-To: <47BAC7BC.7050503@wurmsdobler.org>

On 2/19/08, Peter Wurmsdobler <peter@wurmsdobler.org> wrote:
> Hello,
>
> This topic has already come up several times, but the respective answers
> did not solve the problem for me. What happens is:
>
> mx27# /usr/bin/dbus-daemon --system
> mx27# /usr/sbin/hcid -n -f /etc/bluetooth/hcid.conf
> hcid[1869]: Bluetooth HCI daemon
> hcid[1869]: Could not become the primary owner of org.bluez
> hcid[1869]: Unable to get on D-Bus


I think one of the following cases are possible:

1. An earlier hcid is already running. Check ps ax | grep hcid to confirm.
or
2. You are not root while running hcid .


HTH.

nel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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

  reply	other threads:[~2008-02-19 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 12:12 [Bluez-users] Unable to get on D-Bus Peter Wurmsdobler
2008-02-19 14:57 ` Nel D [this message]
2008-02-19 18:04   ` Peter Wurmsdobler

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=e378cfb20802190657m69936857ob676ad575842c222@mail.gmail.com \
    --to=newatlinux@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