[Bluez-users] Unable to get on D-Bus

[Bluez-users] Unable to get on D-Bus

[Peter Wurmsdobler]

Hello,

This topic has already come up several times, but the respective answers 
did not solve the problem for me. What happens is:

mx27# /usr/bin/dbus-daemon --system
mx27# /usr/sbin/hcid -n -f /etc/bluetooth/hcid.conf
hcid[1869]: Bluetooth HCI daemon
hcid[1869]: Could not become the primary owner of org.bluez
hcid[1869]: Unable to get on D-Bus

Below some more details about the build process and the configuration 
files. My feeling is that the dbus daemon does not read the bluetooth 
related settings.

Many thanks for your help in advance,
peter.


Build history:

dbus:
     get, extract dbus-1.0.2 and cd
     For successful mx27 cross-compilation patch with:
     diff --exclude CVS -uNr dbus-1.0.2/configure.in 
dbus-1.0.2.modified/configure.in
     --- dbus-1.0.2/configure.in	2006-12-11 19:21:19.000000000 +0000
     +++ dbus-1.0.2.modified/configure.in	2008-02-11 10:57:34.000000000 
+0000
     @@ -719,6 +719,7 @@
          exit (0);
      ]])],
                    [ac_cv_have_abstract_sockets=yes],
     +              [ac_cv_have_abstract_sockets=no],
                    [ac_cv_have_abstract_sockets=no]
      )])
      AC_LANG_POP(C)

     /usr/bin/autoconf
     LIBS=-lz ./configure --prefix=/usr --host=arm-linux 
--build=i686-pc-linux-gnu --without-x
     make
     make install

bluez-libs:
     get, extract luez-libs 3.26 and cd
     ./configure --prefix=/usr --host=arm-linux --build=i686-pc-linux-gnu
     make all
     make install

bluez-utils
     get, extract bluez-utils 3.26 and cd
     LIBS=-lz ./configure --prefix=/usr --host=arm-linux 
--build=i686-pc-linux-gnu --with-alsa=/home/peter/mx27/rootfs/usr/lib 
--with-usb=/home/peter/mx27/rootfs/usr/lib --without-openobex 
--without-fuse --enable-bccmd --with-bluez=/home/peter/mx27/rootfs/usr/lib
     perl -pi -e 
's,^sys_lib_search_path_spec=.*,sys_lib_search_path_spec=,' libtool
     make all
     make install


Configuration files are as

/etc/group:
messagebus:x:666:

/etc/passwd:
messagebus:x:666:666:messagebus:/usr/var/run/dbus:/bin/false

/etc/dbus-1/system.conf:
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 
1.0//EN"
  "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
   <type>system</type>
   <user>messagebus</user>
   <fork/>
   <pidfile>/var/run/dbus/pid</pidfile>
   <auth>EXTERNAL</auth>
   <listen>unix:path=/var/run/dbus/system_bus_socket</listen>
   <policy context="default">
     <deny send_interface="*"/>
     <deny receive_interface="*"/>
     <deny own="*"/>
     <allow user="*"/>
     <allow send_destination="org.freedesktop.DBus"/>
     <allow receive_sender="org.freedesktop.DBus"/>
     <allow send_requested_reply="true"/>
     <allow receive_requested_reply="true"/>
   </policy>
   <includedir>system.d</includedir>
   <include ignore_missing="yes">system-local.conf</include>
   <include if_selinux_enabled="yes" 
selinux_root_relative="yes">contexts/dbus_contexts</include>
</busconfig>

/etc/dbus-1/system.d/bluetooth.conf:
<!-- This configuration file specifies the required security policies
      for Bluetooth core service to work. -->
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 
1.0//EN"
  "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
   <!-- ../system.conf have denied everything, so we just punch some 
holes -->
   <policy user="root">
     <allow own="org.bluez"/>
   </policy>
   <policy at_console="true">
     <allow send_destination="org.bluez.Manager"/>
     <allow receive_sender="org.bluez.Manager"/>
     <allow send_path="/org/bluez"/>
     <allow send_destination="org.bluez.Adapter"/>
     <allow receive_sender="org.bluez.Adapter"/>
     <allow send_destination="org.bluez.Service"/>
     <allow receive_sender="org.bluez.Service"/>
     <allow send_destination="org.bluez.Database"/>
     <allow receive_sender="org.bluez.Database"/>
     <allow send_destination="org.bluez.Security"/>
     <allow receive_sender="org.bluez.Security"/>
   </policy>
</busconfig>




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Unable to get on D-Bus

[Nel D]

On 2/19/08, Peter Wurmsdobler <peter@wurmsdobler.org> wrote:
> Hello,
>
> This topic has already come up several times, but the respective answers
> did not solve the problem for me. What happens is:
>
> mx27# /usr/bin/dbus-daemon --system
> mx27# /usr/sbin/hcid -n -f /etc/bluetooth/hcid.conf
> hcid[1869]: Bluetooth HCI daemon
> hcid[1869]: Could not become the primary owner of org.bluez
> hcid[1869]: Unable to get on D-Bus


I think one of the following cases are possible:

1. An earlier hcid is already running. Check ps ax | grep hcid to confirm.
or
2. You are not root while running hcid .


HTH.

nel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Unable to get on D-Bus

[Peter Wurmsdobler]

Hello,

many thanks for the hints.

> 1. An earlier hcid is already running. Check ps ax | grep hcid to confirm.
> 2. You are not root while running hcid .
Neither. The reason was somewhere else.

ltib configures bluez with prefix /usr , but moves some config 
files/directories from /usr/etc to /etc . When I added dbus manually to 
ltib, I ran configure with /usr , too, but without realising that then 
dbus would not find the bluetooth related config file in 
/usr/etc/dbus-1/system.d/, because ltib would have moved it to 
/etc/dbus-1/system.d/.

Solution: make sure that bluez and dbus use the same configuration 
directories and that they are compiled with the same prefix.

One step further. More problems expected.
peter



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users