Comment 23 for bug 1500242

I looked a bit through the logs files this morning and will enumerate my findings per device.

1. Audio A3

The paring attempt is clearly visible in the log files. It first tries to use the automatic-pin-guesser which fails after one attempt and then switches back to ask the connected agent (aka settings application). However it never gets any input back from the agent and therefore the pairing attempt fails (or is denied from the agent which isn't visible from the log file).

That the automatic-pin-guesser is involved is fine and no issue. What seems to be the problem is the communication between the settings application (running the bluez agent) and bluez itself while required to provide a PIN/Passcode for proper authentication.

Around the same time we only see the following output from the settings application:

2015-12-09 08:58:26,823 - WARNING - Failed to start device discovery: "Operation already in progress"
2015-12-09 08:58:29,983 - WARNING - Cancel callback called
2015-12-09 08:58:29,983 - WARNING - Failed to pair with device: "Authentication Failed"

With that we basically know the agent is properly connected but somehow failed to display a popup to let the user acknowledge the pairing or enter a PIN/passcode. What is also interesting is that Matthias describes in his document that he entered the PIN around 8:58.

So there seems to be something really wrong with the communication between agent and bluez.

@Matthias: Are you 100% sure you entered the correct PIN? 1234 as written in your doc doesn't seem to be on the car shows you to enter.

2. Jabra headset

Gets paired correctly via auto-pin-guesser. Otherwise I see what Matthias describes in his document. The device pairs and connects successsfully and then is disconnected because it is turned off. The reconnection attempt from the device doesn't say much:

Dec 9 09:24:38 ubuntu-phablet bluetoothd[887]: src/adapter.c:connected_callback() hci0 device 00:07:A4:00:A7:05 connected eir_len 5
...
Dec 9 09:25:06 ubuntu-phablet bluetoothd[887]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 00:07:A4:00:A7:05 type 0 status 0xe
Dec 9 09:25:06 ubuntu-phablet bluetoothd[887]: src/device.c:device_bonding_complete() bonding (nil) status 0x0e
Dec 9 09:25:06 ubuntu-phablet bluetoothd[887]: src/device.c:device_bonding_failed() status 14

Which basically says there is something going wrong with the security setup. As the last lines say that a authenticated connection couldn't be established.

Reason for this could be multiple things. Either the headset looses the bonding information or we don't save those properly for the next time.

3. Logitec Bluetooth Mouse

Basically I can see in the logs what Matthias is describing in his document. The bonding attempt fails at the lower levels somehow and afterwards it looks a bit like the mouse things its connected and we think we're not as the mouse tries to initiate a connection multiple times and we always deny as we're not paired. Needs further investigation on the lower (HCI) level.

@Matthias: Can you give us the exact model number for the mouse?