I am seeing the same behaviour here, with a Keyspan USB dongle with a Broadcom 2033 chip. Everything worked before upgrading from Jaunty. I found bug #156133 and applied the karmic-proposed package but it still behaves the same.
lsusb:
Bus 002 Device 004: ID 0a5c:2001 Broadcom Corp. Bluetooth Device
Here's what I see in syslog when I try to do a device search from the task bar applet:
Jan 7 13:49:38 mhackett bluetoothd[985]: HCI dev 0 down
Jan 7 13:49:38 mhackett bluetoothd[985]: Adapter /org/bluez/973/hci0 has been disabled
Jan 7 13:49:38 mhackett bluetoothd[985]: Stopping security manager 0
Jan 7 13:49:41 mhackett bluetoothd[985]: HCI dev 0 up
Jan 7 13:49:41 mhackett bluetoothd[985]: Starting security manager 0
Jan 7 13:49:41 mhackett bluetoothd[985]: Adapter /org/bluez/973/hci0 has been enabled
Jan 7 13:49:58 mhackett bluetoothd[985]: Discovery session 0xaf2730 with :1.66 activated
Jan 7 13:49:58 mhackett kernel: [ 3027.668359] hci_cmd_task: hci0 command tx timeout
I am seeing the same behaviour here, with a Keyspan USB dongle with a Broadcom 2033 chip. Everything worked before upgrading from Jaunty. I found bug #156133 and applied the karmic-proposed package but it still behaves the same.
lsusb:
Bus 002 Device 004: ID 0a5c:2001 Broadcom Corp. Bluetooth Device
Here's what I see in syslog when I try to do a device search from the task bar applet:
Jan 7 13:49:38 mhackett bluetoothd[985]: HCI dev 0 down
Jan 7 13:49:38 mhackett bluetoothd[985]: Adapter /org/bluez/973/hci0 has been disabled
Jan 7 13:49:38 mhackett bluetoothd[985]: Stopping security manager 0
Jan 7 13:49:41 mhackett bluetoothd[985]: HCI dev 0 up
Jan 7 13:49:41 mhackett bluetoothd[985]: Starting security manager 0
Jan 7 13:49:41 mhackett bluetoothd[985]: Adapter /org/bluez/973/hci0 has been enabled
Jan 7 13:49:58 mhackett bluetoothd[985]: Discovery session 0xaf2730 with :1.66 activated
Jan 7 13:49:58 mhackett kernel: [ 3027.668359] hci_cmd_task: hci0 command tx timeout