[Dapper] bluez-pin doesn't ask for pin on outgoing pair attempt or incoming pair attempt.

[Toby Smithe]

Binary package hint: bluez-pin

bluez-pin (if run from the console) pops up a dialog asking for a PIN. It appears that hcid just reads the PIN from /etc/bluetooth/pin. It gives this error on startup:

May 21 14:05:09 localhost hcid[11728]: Can't get system message bus name: Connection ":1.43" is not allowed to own the service "org.bluez" due to security policies in the configuration file

Looks like this has something to do with the dbus aspect that bluez-pin has. The log shows this on pair attempt,

May 21 14:03:14 localhost hcid[21768]: pin_code_request (sba=00:0C:76:48:A7:A8, dba=00:0F:DE:A0:6A:05)
May 21 14:03:14 localhost hcid[21768]: link_key_notify (sba=00:0C:76:48:A7:A8, dba=00:0F:DE:A0:6A:05)

so it is pairing.

[Toby Smithe (tsmithe)]

My /etc/bluetooth/hcid.conf

[Ramon Casha (rcasha)]

Not sure if this is the same problem:
On my PC the PIN dialog never showed up. I ran the command "xhost +" and it worked.

[Andres Mujica (andres.mujica)]

maybe related to bug #33357

could you give us the ouput for:

dpkg -l | grep bluez

[Brian Murray (brian-murray)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.