From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] HCID startup error
Date: Wed, 26 Jul 2006 09:31:37 +0200 [thread overview]
Message-ID: <1153899097.746.20.camel@localhost> (raw)
In-Reply-To: <20060718225953.76507.qmail@web51415.mail.yahoo.com>
Hi Manoj,
> I have installed following on CentOS 3.3.
> bluez-libs-3.1.tar.gz
> bluez-utils-3.1.tar.gz
> bluez-firmware-1.2.tar.gz
> bluez-hcidump-1.31.tar.gz
> I see following errors when i start hcid in /var/log/messages/
> hcid[4770]: Bluetooth HCI daemon
> hcid[4770]: Service could not become primary owner
> hcid[4770]: Unable to get on D-Bus
>
> I have started dbus using dbus-daemon and dbus-launch --system. The
> files system-bus-socket and messgebus.pid exist
> under /usr/local/var/run and /usr/local/var/run/dbus/.
>
> Pls let me know what am i missing? Is there any documentation
> available to get bluez working with dbus?
> Any help is greatly appreciated.
this seems like bluez-hcid.conf is not installed properly. If this is
placed in the wrong directory, D-Bus will reject any connections for
org.bluez and thus it won't work.
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
prev parent reply other threads:[~2006-07-26 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 22:59 [Bluez-users] HCID startup error manojt ambe
2006-07-26 7:31 ` Marcel Holtmann [this message]
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=1153899097.746.20.camel@localhost \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.