Unable to become the primary owner

John (J5) Palmieri johnp at redhat.com
Wed Mar 5 17:51:07 PST 2008


On Wed, 2008-03-05 at 10:54 +0530, Paul wrote:
>   Hello list,
> 
>                     I am new to d-bus .I am using d-bus with the bluez
> bluetooth stack on an Arm platform.I am able to start the the dbus
> daemon and the system_bus_socket is getting created.But when I start
> the bluez hci daemon whch uses the dbus,I get errors like "could not
> become the primary owner  ,Unable to get on to dbus ",which is coming
> from a call to dbus_bus_request_name()....and the return value is not
> matching DBUS_REQUEST_NAME_REPLY_PRIMARY_OWNER...
> is this due to any configuration issue?..should I add something to the
> system.conf?
> 
> Thnk you for your time and consideration,
> Warm Regards,
> Paul.

Did you install bluez to a different prefix than D-Bus?  You need to
install the security context file to the sysconfdir of D-Bus.  This is
usually /etc/dbus-1/system.d/ and the file is called bluetooth.conf.

-- 
John (J5) Palmieri <johnp at redhat.com>



More information about the dbus mailing list