All of lore.kernel.org
 help / color / mirror / Atom feed
From: JP Freeley <jpf321@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Unable to get on on the D-Bus
Date: Wed, 26 Jul 2006 05:16:56 -0400	[thread overview]
Message-ID: <44C73308.3010903@gmail.com> (raw)

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

Yes, I have dbus installed and presumably running:
% ps -ef | grep dbus
100       1412     1  0 03:41 ?        00:00:00 /usr/bin/dbus-daemon 
--system

Here are my installed versions:
% apt-show-versions | grep -e dbus -e bluez
libdbus-1-2/sid uptodate 0.62-4
libdbus-glib-1-2/sid uptodate 0.62-4
bluez-utils/sid uptodate 3.1-2
bluez-firmware/sid uptodate 1.0-3
dbus/sid uptodate 0.62-4
bluez-hcidump/sid uptodate 1.31-1
libbluetooth2/sid uptodate 3.1-1

On boot-up here are the reported versions:
Kernel ver. 2.4.32
BlueZ Core 2.4
HCI USB 2.7
l2cap 2.3
rfcomm 1.1

I should mention, I suppose, that I am running low on available disk 
space, I will work towards cleaning that up, could this be the root of 
this error?

Thanks,

jpf

-------------------------------------------------------------------------
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

             reply	other threads:[~2006-07-26  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26  9:16 JP Freeley [this message]
2006-07-26 15:42 ` [Bluez-devel] Unable to get on on the D-Bus Marcel Holtmann
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=44C73308.3010903@gmail.com \
    --to=jpf321@gmail.com \
    --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 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.