Return-Path: From: Marcel Holtmann To: BlueZ users In-Reply-To: References: Date: Sun, 04 Mar 2007 18:36:50 +0100 Message-Id: <1173029811.5752.11.camel@aeonflux.holtmann.net> Mime-Version: 1.0 Subject: Re: [Bluez-users] pin code 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 Hi Kelvin, > i am faced with the sam problems as KS H. I have also cross compiled dBus > and Bluez Util for ARM using Scratchbox. > I followed the similar steps provided by Prabhu. However, I do not have the > message.pid entry in /var/run but have an additional "pid" entry in > /var/run/dbus. > > And when i try to execute hcid i received the following error: > # hcid -n -f /etc/bluetooth/hcid.conf > hcid[790]: Bluetooth HCI daemon > hcid[790]: Can't open system message bus connection: Failed to connect to > socket /var/run/dbus/system_bus_socket: Connection refused > hcid[790]: Unable to get on D-Bus > > Please advice. Thank you this can mean two things. Either the system bus is not running or the security settings for hcid to claim the org.bluez namespace are not correctly set. 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