Bluetooth Secure Simple Pairing SSP Broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Since installing Ubuntu 11.10 (with Linux 3.0), Secure Simple Pairing (SSP) is broken and will not allow my SSP headset (Samsung HM1000, EDR + 2.1) to reconnect after initial pairing and disconnect. I am able to pair and connect at first. Before I diconnect, everything works as expected. But after disconnecting, I am no longer able to re-connect the headset. I have to un-pair then re-pair the device to connect again to get it working. After re-pairing the headset it stays connected until I disconnect. Then again after disconnecting, I am again not able to connect.
I have been using the same BT usb dongle and BT headset in Ubuntu 10.10, 11.04, and 11.10. Everything worked fine in Ubuntu 10.10 and 11.04, which I think were based on Linux Kernel 2.6.35 and 2.6.38 respectively. In those versions, I was able to pair and connect / disconnect / connect without issue.
I posted an email on the Bluez developer mailing list and it seems that there is a known issue in the way SSP pairing is working (http://
I am able to work around the issue by running the command: sudo hciconfig hci0 sspmode 0 to disable sspmode to default back to legacy connection. However, after rebooting, I again have to disable sspmode in order to connect the headset. Seems like this is a very basic use case that left uncorrected can result in very poor user experience.
affects: | bluez (Ubuntu) → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: oneiric |
affects: | linux (Ubuntu) → bluez (Ubuntu) |
Changed in bluez (Ubuntu): | |
status: | Confirmed → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 931860
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.