Return-Path: Message-ID: <01f301c8e787$6ebf2140$6701a8c0@freqonedev> From: "David Stockwell" To: "BlueZ users" References: Date: Wed, 16 Jul 2008 16:03:40 -0500 MIME-Version: 1.0 Subject: Re: [Bluez-users] bluez-utils 3.36: Unable to get on D-Bus Reply-To: BlueZ users List-Id: BlueZ users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-users-bounces@lists.sourceforge.net Errors-To: bluez-users-bounces@lists.sourceforge.net I have also seen this since 3.35, and suspect that somehow the name org.bluez is not being released when shutting down the previous version. This does not make much sense though, sinee when the hcid shuts down or dies, the name should be released as a basic function of DBus. When I have seen this recently, I just reboot...all my years working with Micro$oft... DS ----- Original Message ----- From: "Voni Hakau" To: "BlueZ users" Sent: Wednesday, July 16, 2008 10:34 AM Subject: [Bluez-users] bluez-utils 3.36: Unable to get on D-Bus > Hi all, > > I get the following error: > > # hcid -n -s -d > hcid[467]: Bluetooth HCI daemon > hcid[467]: Enabling debug information > hcid[467]: Unable to get on D-Bus > > Can someone please help me how to debug this ? > > I use bluez-utils 3.36 with the newest d-bus. > > I got d-bus up and running (dbus-daemon --system is running, and I the > UNIX domain socket file is created). > > Any ideas ? > > Thank you > Voni > > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users