From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Unable to get on on the D-Bus
Date: Wed, 26 Jul 2006 17:42:11 +0200 [thread overview]
Message-ID: <1153928531.5075.0.camel@localhost> (raw)
In-Reply-To: <44C73308.3010903@gmail.com>
Hi,
> I have moved to the debian "sid" branch as it has 3.1 bluez included.
>
> When I first apt-get'd the necessary packages everything seemed to work OK.
> After REBOOT I am getting the following messages about HCID:
>
> Jul 27 03:41:37 hcid[1460]: Bluetooth HCI daemon
> Jul 27 03:41:37 sdpd[1462]: Bluetooth SDP daemon
> Jul 27 03:41:37 hcid[1460]: Service could not become the primary owner.
> Jul 27 03:41:37 hcid[1460]: Unable to get on D-Bus
> Jul 27 03:41:38 dund[1481]: Bluetooth DUN daemon version 3.1
do you have a correct installed bluez-hcid.conf for the D-Bus service?
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-26 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 9:16 [Bluez-devel] Unable to get on on the D-Bus JP Freeley
2006-07-26 15:42 ` Marcel Holtmann [this message]
2006-07-26 18:18 ` Filippo Giunchedi
2006-07-26 20:06 ` JP Freeley
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=1153928531.5075.0.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@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