not allowed to own "org.bluez" due to security policies

Bug #49105 reported by Carl Karsten
This bug report is a duplicate of:  Bug #33338: bluez-utils can't start in dbus mode. Edit Remove
6
Affects Status Importance Assigned to Milestone
bluez-utils (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: bluez-utils

from <email address hidden>
Subject: Re: [Bluez-users] PM325 by LG cell phone - pairing failed

> > I am trying to pair my phone to my ubuntu/dapper laptop .
> > carl@asus17:~$ lsusb
> >
> > Bus 003 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth
> > carl@asus17:~$ cat /etc/bluetooth/pin
> > 1234
> > carl@asus17:~$ sudo /etc/init.d/bluez-utils start
> >
> > On the phone: menu, bluetooth, add new, Searching and Pairing,
> > it shows asus17-0, I select that, phone prompts "Enter PIN code", I
> > enter 1234<Next> and within a second get "pairing failed"
> >
> > guessing because of this:
> >
> > Jun 9 00:37:42 localhost gconfd (root-7749): starting (version 2.14.0),
> > pid 7749 user 'root'
> > Jun 9 00:37:42 localhost gconfd (root-7749): Resolved address
> > "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
> > configuration source at position 0
> > Jun 9 00:37:42 localhost gconfd (root-7749): Resolved address
> > "xml:readwrite:/root/.gconf" to a writable configuration source at
> > position 1
> > Jun 9 00:37:42 localhost gconfd (root-7749): Resolved address
> > "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
> > configuration source at position 2
> > Jun 9 00:37:42 localhost gconfd (root-7749): Resolved address
> > "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only
> > configuration source at position 3
> > Jun 9 00:37:42 localhost gconfd (root-7749): Resolved address
> > "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration
> > source at position 4
> > Jun 9 00:38:42 localhost gconfd (root-7749): GConf server is not in
> > use, shutting down.
> > Jun 9 00:38:42 localhost gconfd (root-7749): Exiting
> >
> > Jun 9 01:03:08 localhost hcid[8572]: Bluetooth HCI daemon
> > Jun 9 01:03:08 localhost hcid[8572]: Can't get system message bus name:
> > Connection ":1.15" is not allowed to own the service "org.bluez" due to
> > security policies in the configuration file
> > Jun 9 01:03:08 localhost hcid[8572]: Starting security manager 0
> > Jun 9 01:03:08 localhost sdpd[8577]: Bluetooth SDP daemon
> >

for the "security policies" error you should really file a bug report
with Ubuntu. - Marcel Holtmann

Revision history for this message
Andriy Tymchenko (silpol) wrote : seems like I have same problem with Dapper

Nov 4 21:48:25 localhost hcid[8150]: Bluetooth HCI daemon
Nov 4 21:48:25 localhost sdpd[8152]: init_server: binding L2CAP socket: Address already in use
Nov 4 21:48:25 localhost sdpd[8152]: main: Server initialization failed
Nov 4 21:48:25 localhost hcid[8150]: Can't get system message bus name: Connection ":1.13" is not allowed to own the service "org.bluez" due to security policies in the configuration file
Nov 4 21:48:26 localhost hcid[8158]: Can't init device hci0: Permission denied (13)
Nov 4 21:48:26 localhost hcid[8159]: Can't set scan mode on hci0: Permission denied (13)
Nov 4 21:48:26 localhost hcid[8159]: Can't set auth on hci0: Permission denied (13)
Nov 4 21:48:26 localhost hcid[8159]: Can't set encrypt on hci0: Permission denied (13)
Nov 4 21:48:26 localhost hcid[8150]: Starting security manager 0

Revision history for this message
inos (guehring+ubuntu) wrote :

i can confirm this on dapper with exactly the same output...
and i am sure... there was a time about 2 month ago, all worked perfectly!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.