Hi Prabhu
I have a question. I have cross compiled dbus-0.93 and flashed the image in my hardware platform. Now when i run dbus-daemon --system it gives me an error
Failed to open connection to system message bus: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
I am a bit confused here because you write that system_bus_socket is created when dbus-daemon is started. However in my case it is expecting the socket file to be present when I start dbus-daemon.

Can you please clarify how do i solve this problem?
 

Regards,
Sumeet

 


From: bluez-users-bounces@lists.sourceforge.net [mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Prabhu nath
Sent: Friday, January 26, 2007 11:15 AM
To: BlueZ users
Subject: Re: [Bluez-users] pin code

You have to cross-compile dbus-1.0, and start dbus-daemon before executing hcid.
dbus-daemon --system
 
While cross-compiling dbus-1.0 and bluez-utils, pass the following parameters for the configure script.
--localstatedir=/var --sysconfdir=/etc
 
Once you do this, by default hcid will look for hcid.conf in /etc/bluetooth directory.
 
 
Warning. Take a backup of /etc/dbus-1 and /etc/bluetooth, because this will overwrite the previous config, which was already present in ur system.
 
Run make install for dbus, and u need not run make install for bluez-utils. U can directly copy the hcid.conf and blue-hcid.conf to /etc/bluetooth and /etc/dbus-1/system.d directory respectively.
 
Now, when u start dbus-daemon --system, it will create a system_bus_socket in /var/run/dbus and it will create a message.pid in /var/run/.
 
next, when u start hcid, u should not get problem.
 
-Prabhu
 


 
On 1/23/07, KS H <kspam1234@yahoo.com.hk> wrote:
Dear

I cross compile the bluez3.8 and try to setup the bluetooth in arm. I connect the arm with CSR BC03 with BCSP configuration. I am able to make the Bluez discoverable and try to pair bluez. however i found that there is no pin respond from Bluez. So i try to configure bluez using hcid.

> hcid -n -f /etc/bluetooth/hcid.conf

it return

hcid[481]: Can't connect to system message bus: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket:  No such file or directory
hcid[481]: Unable to get on D-Bus

My question
1. where can I found the missing file and what is that used for?
2. Is there any method to repsond the pin request other than using hcid

Regards
SH

_______________________________________
YM - 離線訊息
就算你沒有上網,你的朋友仍可以留下訊息給你,當你上網時就能立即看到,任何說話都冇走失。
http://messenger.yahoo.com.hk


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