From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcid <-> dbus problem
Date: Mon, 04 Jun 2007 17:19:15 +0200 [thread overview]
Message-ID: <1180970355.13429.45.camel@violet> (raw)
In-Reply-To: <e96e9eeb0706040653t2a6f8da5lbc7399932ff6fcbb@mail.gmail.com>
Hi Voni,
> I can't run bluez in my platform. i tried this series of commands:
>
> dbus-daemon --system (seems to work)
> hcid -nsd
>
> that last command doesn't work, i get:
> Dec 31 18:48:16 8 daemon.info hcid[945]: Bluetooth HCI daemon
> Dec 31 18:48:17 8 daemon.err hcid[945]: Could not become the primary
> owner of org.bluez
> Dec 31 18:48:17 8 daemon.err hcid[945]: Unable to get on D-Bus
>
> I even tried:
> dbus-daemon --config-file /etc/dbus-1/system.d/bluetooth.conf
>
> but it fails with the message:
> Failed to start message bus: Configuration file needs one or more
> <listen> elements giving addresses
this looks wrong. The bluetooth.conf is only one of the security rules
used by dbus-daemon. You must make sure the compiled in paths are all
correct. Ask the D-Bus guys for more help.
> (running sdpd alone does not fail btw)
Of course, but sdpd is obsoleted.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-06-04 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:53 [Bluez-users] hcid <-> dbus problem Voni Hakau
2007-06-04 15:19 ` Marcel Holtmann [this message]
2007-06-04 15:30 ` 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=1180970355.13429.45.camel@violet \
--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.