Am I stupid or something?  Where, pray tell, can I find this "fix"?

Bruce


On Aug 16, 2009, at 7:45 AM, Brian Rogers wrote:

> A fix for one Bluetooth issue has already been committed and released,
> so "Fix Released" is the proper state for this bug report.
>
> If you still have the same symptoms even with the fix and have  
> reported
> one of the bugs that is marked as a duplicate of this one, you can
> undupe your own bug report and reopen that. Otherwise, if you are  
> still
> experiencing Bluetooth issues, please file a new bug report. There are
> more issues to fix, and they all need to be tracked in their own bug
> reports.
>
> Oh, and if your symptoms have changed in any way after this fix, be  
> sure
> to file a new bug and not reopen a duplicated bug report, so you don't
> cause confusion.
>
> -- 
> Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
> https://bugs.launchpad.net/bugs/268502
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Linux Kernel: In Progress
> Status in “bluez” package in Ubuntu: Invalid
> Status in “linux” package in Ubuntu: Fix Released
> Status in bluez in Ubuntu Intrepid: Invalid
> Status in linux in Ubuntu Intrepid: Fix Committed
> Status in bluez in Ubuntu Jaunty: Invalid
> Status in linux in Ubuntu Jaunty: Fix Released
> Status in “bluez” package in Debian: Fix Committed
> Status in “bluez-utils” package in Debian: Fix Committed
>
> Bug description:
> SRU justification:
>
> Impact: A series of bluetooth dongles [1] do not work properly with  
> the new
>        btusb driver which replaced usb_hci. This has been fixed  
> upstream
>        (2.6.29-rc3). The required changes are all local to the btusb  
> driver.
>
> Fix: The following three patches are required to fix this (two as  
> prerequisite
>     and one for the actual fix). The fix deviates from upstream by  
> the change
>     of a version number and the missing resume part which does not  
> exist for
>     Intrepid nor Jaunty.
>
> Test: Fix has been tested by bug reporters.
>
> ---
>
> Bluetooth doesn't work for at least the following devices:
> ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth  
> Adapter
> ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
> ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
> ID 0a5c:200a Broadcom Corp. Bluetooth dongle
>
> They don't work properly with the newer btusb driver, which replaced  
> hci_usb by default in 2.6.27. This hasn't been fixed upstream as of  
> v2.6.29-rc3.
>
> Original message below:
>
> Association with Bluetooth works using kernel 2.6.26, since the  
> updates to 2.6.27 (both -1 and -2) association fails. I can scan and  
> see bluetooth devices but not pair.
>
> Using my phone, I start the association process, the phone asks for  
> a passkey, and in 2.6.26 the popup window appears normally allowing  
> me to enter the passkey. In 2.6.27 the dialog box never appears.
>
> If I use hcitool:
>
> :~$ sudo hcitool cc 00:1B:59:96:A6:DD
> :~$ sudo hcitool auth 00:1B:59:96:A6:DD
> HCI authentication request failed: Connection timed out
>
> the dialog box appears very very briefly then vanishes.
>
> dmesg shows a couple of problems:
>
> [25791.306170] btusb_intr_complete: hci0 urb ffff88004dd0fb40 failed  
> to resubmit (19)
> [25791.315446] btusb_send_frame: hci0 urb ffff880048542840  
> submission failed
>
> and the syslog shows that there was an attempt to associate:
>
> Sep 23 08:16:59 charlie hcid[5903]: link_key_request  
> (sba=00:11:67:9C:59:B5, dba=00:1B:59:96:A6:DD)
> Sep 23 08:16:59 charlie hcid[5903]: pin_code_request  
> (sba=00:11:67:9C:59:B5, dba=00:1B:59:96:A6:DD)