I've added deb http://ppa.launchpad.net/blueman/ppa/ubuntu karmic main
and ran apt-get update;apt-get install blueman, it removed
gnome-bluetooth but i'm still having timeout messages.
Could you please explain a bit longer how did you manage to solve it?

Thanks!

2010/1/12 Dmitry Diskin <email address hidden>:
> BT (KY-BT100 dongle) worked right after fresh install of Karmic, then I
> installed blueman from Karmic repositories, and seems that it caused the
> above problems. Tried to remove blueman completely - did not help.
> Booting from standard Karmic live CD - BT worked. The problem was solved
> after installing blueman from PPA, which removed gnome-bluetooth. It
> worked even before I updated bluez from the same PPA.
>
> When I installed blueman originally from Karmic repositories, it did not
> remove gnome-bluetooth, and I had two bluetooth icons for some time
> (both disabled).
>
> --
> 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” source package in Intrepid: Invalid
> Status in “linux” source package in Intrepid: Fix Released
> Status in “bluez” source package in Jaunty: Invalid
> Status in “linux” source package in Jaunty: Fix Released
> Status in “bluez” package in Debian: New
> Status in “bluez-utils” package in Debian: New
>
> 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)
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/linux/+bug/268502/+subscribe
>