Some bluetooth dongles don't work anymore

Bug #289836 reported by isecore on 2008-10-27
186
This bug affects 34 people
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Unassigned
Nominated for Intrepid by Jonathan Ernst

Bug Description

This is a hardware support regression between Hardy and Intrepid

== Regression details ==
Discovered in version: Intrepid
Last known good version: Hardy

== Affected chips/dongles ==
0a5c:200a Broadcom Corp. Bluetooth dongle
2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth

== Known workaround ==
none (besides using Ubuntu Hardy)

== Description ==
I upgraded from Hardy x64 to Intrepid x64 a few days back. After upgrade bluetooth doesn't work. No icon in the tray, nothing. After restarting the bluetooth service with /etc/init.d/bluetooth restart the icon pops up, but it's a complete dud. Cannot set my computers bluetooth-name, can't pair devices, can't send or receive files. Nothing.

This is what's logged in daemon.log:

Oct 27 13:37:22 superbeast bluetoothd[14641]: Bluetooth daemon
Oct 27 13:37:22 superbeast bluetoothd[14641]: Starting SDP server
Oct 27 13:37:22 superbeast bluetoothd[14641]: Starting experimental netlink support
Oct 27 13:37:22 superbeast bluetoothd[14641]: Failed to find Bluetooth netlink family
Oct 27 13:37:22 superbeast bluetoothd[14641]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Oct 27 13:37:22 superbeast bluetoothd[14641]: bridge pan0 created
Oct 27 13:37:22 superbeast bluetoothd[14641]: HCI dev 0 registered
Oct 27 13:37:22 superbeast bluetoothd[14641]: HCI dev 0 already up
Oct 27 13:37:27 superbeast bluetoothd[14641]: Can't read version info for /org/bluez/hci0: Connection timed out (110)
Oct 27 13:37:27 superbeast bluetoothd[14641]: Starting security manager 0
Oct 27 13:37:32 superbeast bluetoothd[14648]: Can't set link policy on hci0: Connection timed out (110)

lsusb lists the device as:

Bus 002 Device 004: ID 0a5c:200a Broadcom Corp. Bluetooth dongle

How do I check if a driver is loaded for it? lsmod | grep blue gives me:

bluetooth 70820 28 bnep,sco,rfcomm,l2cap,btusb

but that doesn't change even if I yank the dongle from my computer.

I have the latest updates to Intrepid applied.

Scott Kitterman (kitterman) wrote :

Is this Ubuntu or Kubuntu?

isecore (isecore) wrote :

Oh, my bad. It's plain Ubuntu, running Gnome.

Scott Kitterman (kitterman) wrote :

OK. If it was Kubuntu, I'd know why. No idea about Ubuntu.

isecore (isecore) wrote :

Any news on this? I'd really like my bluetooth back.

If you need anything, just ask. I'm not psychic :)

Loic Dreux (loic.dreux) wrote :

I've same bug with same materiel :

bob@tethys:~$ lsusb | grep Bluetooth
Bus 005 Device 004: ID 0a5c:200a Broadcom Corp. Bluetooth dongle

I'm run on Intrepid x86, I've the bluetooth icon on my tray but I can't connect to my phone : my computer doesn't see my phone, my phone see my computer but when I try to connect the last with the first, I've got an error message.

Perhaps It's a problem from the driver of Broadcom Bluetooth dongle or the new Bluetooth Gnome package.

Jonathan Ernst (jonathan.ernst) wrote :

Same bug with another similar bluetooth dongle (I think it's the same chip) :
2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

dmesg :
[ 339.011026] hci_cmd_task: hci0 command tx timeout

daemon.log
Oct 29 21:58:43 jernst-desktop bluetoothd[6499]: HCI dev 0 registered
Oct 29 21:58:43 jernst-desktop bluetoothd[6499]: HCI dev 0 up
Oct 29 21:58:48 jernst-desktop bluetoothd[6499]: Registered interface org.bluez.Service on path /org/bluez/hci0
Oct 29 21:58:53 jernst-desktop bluetoothd[6499]: Can't write class of device: Connection timed out (110)

jernst@jernst-desktop:~$ sudo hcitool scan
Scanning ...
Inquiry failed: Connection timed out

jernst@jernst-desktop:~$ sudo hciconfig hci0 reset
jernst@jernst-desktop:~$ sudo hcitool scan
Scanning ...
 00:19:7D:EA:A6:14 n/a

ukblacknight (tom-blacknight) wrote :

I'm experiencing the same bug. I've got a Belkin F8T009, on 8.04 (32bit) on Gnome.

lsusb:
Bus 001 Device 008: ID 0a5c:200a Broadcom Corp. Bluetooth dongle

The icon is displayed to start with, but then disappears when I try to do anything with it.

ukblacknight (tom-blacknight) wrote :

Edit: Sorry, I meant 8.10!

Jakub Nietrzeba (gluth) wrote :

The same bug, icon is hiding when dongle is off, showing when on, but nothing can be done with it.

lsusb:
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

deamon.log (plug-out, plug-in):
Nov 2 00:46:51 skeleton bluetoothd[5418]: HCI dev 0 down
Nov 2 00:46:51 skeleton bluetoothd[5418]: Unregistered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 2 00:46:51 skeleton bluetoothd[5418]: Unregistered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 2 00:46:51 skeleton bluetoothd[5418]: Unregistered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 2 00:46:51 skeleton bluetoothd[5418]: Adapter /org/bluez/hci0 has been disabled
Nov 2 00:46:51 skeleton bluetoothd[5418]: Stopping security manager 0
Nov 2 00:46:51 skeleton bluetoothd[5418]: HCI dev 0 unregistered
Nov 2 00:46:51 skeleton bluetoothd[5418]: Unregister path: /org/bluez/hci0
Nov 2 00:47:04 skeleton bluetoothd[5418]: HCI dev 0 registered
Nov 2 00:47:04 skeleton bluetoothd[5418]: HCI dev 0 up
Nov 2 00:47:04 skeleton bluetoothd[5418]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 2 00:47:04 skeleton bluetoothd[5418]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 2 00:47:04 skeleton bluetoothd[5418]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 2 00:47:04 skeleton bluetoothd[5418]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 2 00:47:04 skeleton bluetoothd[5418]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 2 00:47:04 skeleton bluetoothd[5418]: Failed to listen on control channel
Nov 2 00:47:04 skeleton bluetoothd[5418]: Adapter /org/bluez/hci0 has been enabled
Nov 2 00:47:04 skeleton bluetoothd[5418]: Starting security manager 0

It was working nicely before update, and it is working on another computer.

emersom (emersomrc) wrote :

My bluetooth doesn't work either after upgrading to 8.10 intrepid x86. It was working on Hardy.

Dominique Meeùs (dominiquem) wrote :

Ubuntu 8.10, bluez 4.12-0ubuntu5
I have a Bluetooth device that was functioning perfectly under 8.04
It is still there :
# lsusb
Bus 001 Device 005: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

hciconfig gives a "result" but actually null :
# hciconfig
hci0: Type: USB
 BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
 DOWN
 RX bytes:0 acl:0 sco:0 events:0 errors:0
 TX bytes:18 acl:0 sco:0 commands:6 errors:0

hcitool gives no result:
# hcitool dev
Devices:

and hiciconfig cannot start hci0 :
# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

Here are the bluetooth messages in daemon.log :
Nov 4 18:07:20 library bluetoothd[5320]: Bluetooth daemon
Nov 4 18:07:20 library bluetoothd[5320]: Starting SDP server
Nov 4 18:07:20 library bluetoothd[5320]: Starting experimental netlink support
Nov 4 18:07:20 library bluetoothd[5320]: Failed to find Bluetooth netlink family
Nov 4 18:07:20 library bluetoothd[5320]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
Nov 4 18:07:20 library bluetoothd[5320]: bridge pan0 created
Nov 4 18:07:20 library bluetoothd[5320]: HCI dev 0 registered
Nov 4 18:07:20 library bluetoothd[5320]: HCI dev 0 up
Nov 4 18:07:20 library bluetoothd[5320]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 4 18:07:25 library bluetoothd[5320]: Can't write class of device: Connection timed out (110)
Nov 4 18:07:30 library bluetoothd[5320]: Can't write class of device: Connection timed out (110)
Nov 4 18:07:34 library bluetoothd[5320]: Can't write class of device: Connection timed out (110)
Nov 4 18:07:34 library bluetoothd[5320]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 4 18:07:39 library bluetoothd[5320]: Can't write class of device: Connection timed out (110)
Nov 4 18:07:39 library bluetoothd[5320]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 4 18:07:45 library bluetoothd[5320]: Can't write class of device: Connection timed out (110)
Nov 4 18:07:45 library bluetoothd[5320]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 4 18:07:50 library bluetoothd[5320]: Can't write class of device: Connection timed out (110)
Nov 4 18:07:50 library bluetoothd[5320]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 4 18:07:50 library bluetoothd[5320]: Adapter /org/bluez/hci0 has been enabled
Nov 4 18:07:50 library bluetoothd[5320]: Starting security manager 0
Nov 4 18:42:32 library bluetoothd[5320]: Unable to start periodic inquiry: Connection timed out (110)
# bluetoothd restart
Nov 4 19:04:30 library bluetoothd[7532]: Bluetooth daemon
Nov 4 19:04:30 library bluetoothd[7532]: Unable to get on D-Bus
# bluetoothd stop
Nov 4 19:06:04 library bluetoothd[7554]: Bluetooth daemon
Nov 4 19:06:04 library bluetoothd[7554]: Unable to get on D-Bus
# bluetoothd start
Nov 4 19:07:00 library bluetoothd[7568]: Bluetooth daemon
Nov 4 19:07:00 library bluetoothd[7568]: Unable to get on D-Bus

Dominique Meeùs (dominiquem) wrote :

After I start the computer, the situation is a "null" down device:
# hciconfig
hci0: Type: USB
 BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
 DOWN
 RX bytes:0 acl:0 sco:0 events:0 errors:0
 TX bytes:3 acl:0 sco:0 commands:1 errors:0

If I unplug the USB dongle an plug it again, it becomes a "real" up and running device:
# hciconfig
hci0: Type: USB
 BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING
 RX bytes:657 acl:0 sco:0 events:18 errors:0
 TX bytes:327 acl:0 sco:0 commands:21 errors:0

This is much better. But it is still not functioning:
# hcitool scan
Scanning ...
Inquiry failed: Connection timed out

though my mobile Bluetooth telephone is Bluetooth visible (and has always connected without problem under 8.04)

Jacy Gaddis (nightmarejg) wrote :

Same here.

Bluetooth icon appears, but I'm unable to change any preferences (visability, name) or connect any Bluetooth devices.
In Ibex with kernel 2.6.24-19 Bluetooth works great, but my Nvidia won't work right so I'm stuck with non-working bt.

With only the bt dongle plugged in:

$ lsusb
Bus 002 Device 011: ID 0a5c:3503 Broadcom Corp.
Bus 002 Device 010: ID 0a5c:3502 Broadcom Corp.
Bus 002 Device 009: ID 0a5c:2009 Broadcom Corp. Bluetooth Controller
Bus 002 Device 008: ID 0a5c:3535 Broadcom Corp.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Christophe Charlot (c-charlot) wrote :

And it's not working for me too :
Ubuntu 8.10 (upgraded from Hardy with blueman installed)
I did uninstall blueman and reinstalled the 'standard' bluetooth packages

My symptoms are a bit different : I can scan ans see other devices, but I can't pair any or transfer files..

$ lsusb | grep Blu
Bus 004 Device 003: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth

daemon.log (when switching on bluetooth)
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: HCI dev 0 registered
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: HCI dev 0 up
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Failed to listen on control channel
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Adapter /org/bluez/hci0 has been enabled
Nov 6 00:47:03 christophe-laptop bluetoothd[7046]: Starting security manager 0

daemon.log (when swithcing off bluetooth)
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: HCI dev 0 down
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: Unregistered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: Unregistered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: Unregistered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: Adapter /org/bluez/hci0 has been disabled
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: Stopping security manager 0
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: HCI dev 0 unregistered
Nov 6 00:49:53 christophe-laptop bluetoothd[7046]: Unregister path: /org/bluez/hci0

And the output of DMESG when switching on then off bluetooth :
[19951.260162] usb 4-1: new full speed USB device using uhci_hcd and address 7
[19951.428041] usb 4-1: configuration #1 chosen from 1 choice
[19982.272236] usb 4-1: USB disconnect, address 7
[19982.275191] btusb_intr_complete: hci0 urb f18e6d80 failed to resubmit (19)
[19982.275792] btusb_send_frame: hci0 urb f1a0ad00 submission failed

Hope this can help..

Christophe Charlot (c-charlot) wrote :

Oops... I was not correct in my previous post.

BT seems to be working OK now to see and browse my mobile phone (I this reinstalling all the BT packages did the trick).
I also managed to connect a BT headset without any problem.

But my BT mouse still doesn't connect.
Even I I remove it from the paired list, when I rty to pair it, the computer telles me it is correctly paired, but the mouse stays in pairing mode...
And If I want it to be working, i need to do : sudo hidd --search (when mouse still in pairing mode).

Jakub Nietrzeba (gluth) wrote :

I have just removed blueman (completely, with config) and I can send files to devices, pair with them. It looks like blueman (it register itself as security manger for bluetooth) cannot act well with new bluetooth applets from 8.10.

emersom (emersomrc) wrote :

For me, in the other hand, bluetooth have paired only after I installed the package for blueman. I've installed this package https://launchpad.net/%7Eblueman/+archive/+files/blueman_0.6-r121-0ubuntu3~ppa1i_i386.deb. This wiil install bluez3-utils and bluetooth3.

emersom (emersomrc) wrote :
Dominique Meeùs (dominiquem) wrote :

No improvement with bluez 4.17
I added "deb http://ppa.launchpad.net/blueman/ubuntu intrepid main" to my repositories and installed blueman. This seems to force the uninstallation of the buggy bluez 4 packages and install some bluez 3 packages instead.
I had had error messages about obex. I installed also gnome-vfs-obexftp and obexftp. I do not know if this is relevant.
I has some problem with pairing. I tried different ways with blueman and with wammu until it succeeded. As a result, I am unable to describe when and why it eventually succeeded. (Pairing is very poorly documented.)
Now my wammu connects to the phone automatically as with 8.04. I then uninstalled blueman because I was only interested in bluez 3, not really with blueman and it makes no difference to the connexion with wammu.
Sorry that I had to drop bluez 4 but I really need to synchronize calendar and tasks from my phone with lightning in Thunderbird and I cannot wait for bluez 4.18, 4.19, 4.20…

description: updated
John Doe (johndoe32102002) wrote :
Download full text (4.2 KiB)

Bluetooth used to work on Ubuntu Hardy (8.04, 32-bit), and now fails on Ubuntu Intrepid (8.10, 32-bit).

user@COMPUTER:~$ lsusb | grep Bluetooth
Bus 003 Device 003: ID 047d:105d Kensington PocketMouse Bluetooth

user@COMPUTER:~$ sudo hcitool scan
[sudo] password for user:
Scanning ...
Inquiry failed: Connection timed out

user@COMPUTER:~$ sudo hciconfig hci0 reset

user@COMPUTER:~$ sudo hcitool scan
Scanning ...
 <mac address here> n/a

user@COMPUTER:~$ sudo hciconfig
hci0: Type: USB
 BD Address: <mac address here> ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING
 RX bytes:1505 acl:0 sco:0 events:50 errors:0
 TX bytes:1263 acl:0 sco:0 commands:60 errors:0

Here is my /var/log/daemon.log before and after the above commands:

Nov 16 11:01:24 COMPUTER bluetoothd[5031]: HCI dev 0 registered
Nov 16 11:01:25 COMPUTER bluetoothd[5031]: HCI dev 0 up
Nov 16 11:01:35 COMPUTER bluetoothd[5031]: Can't write inquiry mode for /org/bluez/hci0: Connection timed out (110)
Nov 16 11:01:40 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:01:55 COMPUTER last message repeated 3 times
Nov 16 11:01:55 COMPUTER bluetoothd[5031]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 16 11:02:00 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:02:00 COMPUTER bluetoothd[5031]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Adapter /org/bluez/hci0 has been enabled
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Starting security manager 0
Nov 16 11:02:11 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:03:07 COMPUTER NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: HCI dev 0 down
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Unregistered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Unregistered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Unregistered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Adapter /org/bluez/hci0 has been disabled
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Stopping security manager 0
Nov 16 11:08:25 COMPUTER bluetoothd[5031]: HCI dev 0 up
Nov 16 11:08:35 COMPUTER bluetoothd[5031]: Can't write inquiry mode for /org/bluez/hci0: Connection timed out (110)
Nov 16 11:08:40 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:08:55 COMPUTER last message repeated 3 times
Nov 16 11:08:55 COMPUTER bluetoothd[5031]: Failed to lis...

Read more...

BrowneR (chris-scotland) wrote :

My bluetooth also malfunctions. I managed to get it to pair with my phone once after emptying /var/lib/bluetooth/ however it wont do it again.

I'm not so sure mine is a kernel/driver problem as the phone does see the pc and my pc also sees the phone however i cannot pair or use file transfer/modem or HID capabilities.

lsusb:

Bus 004 Device 046: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

syslog:

Nov 16 19:58:42 chris-laptop kernel: [89169.800186] usb 4-2: new full speed USB device using uhci_hcd and address 46
Nov 16 19:58:43 chris-laptop kernel: [89169.972498] usb 4-2: configuration #1 chosen from 1 choice
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: HCI dev 0 registered
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: HCI dev 0 up
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Failed to listen on control channel
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.Input on path /org/bluez/hci0/dev_00_16_B8_63_A7_FA
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.Network on path /org/bluez/hci0/dev_00_16_B8_63_A7_FA
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Registered interface org.bluez.Serial on path /org/bluez/hci0/dev_00_16_B8_63_A7_FA
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Adapter /org/bluez/hci0 has been enabled
Nov 16 19:58:43 chris-laptop bluetoothd[5618]: Starting security manager 0
Nov 16 20:02:59 chris-laptop kernel: [89426.666972] hci_cmd_task: hci0 command tx timeout
Nov 16 20:02:59 chris-laptop bluetoothd[5618]: Discovery session 0xb9a29660 with :1.456 activated
Nov 16 20:03:02 chris-laptop bluetoothd[5618]: Discovery session 0xb9a29660 with :1.456 deactivated
Nov 16 20:03:14 chris-laptop kernel: [89441.560035] hci_cmd_task: hci0 command tx timeout

Felix Oghină (felix.oghina) wrote :

$ lsusb | grep Blue
Bus 004 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

I can connect from the phone to the computer (pair, send files, etc) but not the other way around. From the computer I can't pair, can't send files, etc. Used to work in Hardy. What happened??

okubax (xappeal) wrote :

I had the same problems when I upgraded to intrepid, I couldn't send files to my phone through bluetooth. But I just installed gnome-bluetooth and everything seems to be working proper now. I can send/receive files and browse files on my phone too.

Felix Oghină (felix.oghina) wrote :

okubax: what type of USB hardware do you have? What's the output of:
lsusb | grep Blue

(If you don't trust me about that command, here's what it does:
   - lsusb - lists all usb devices found on your system
   - grep Blue - takes that listing and only displays those entries that contain the word Blue)

description: updated
Felix Oghină (felix.oghina) wrote :

Added 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter to == Affected chips ==.

Znupi a écrit ce qui suit, le 17/11/08 18:41 :
> [...]
> == Known workaround ==
> none (besides using Ubuntu Hardy) [...]

The problem is bluez 4, not the whole of Intrepid. There is indeed a
workaround other than using Hardy: using bluez 3 under Intrepid. This is
what I described in my post 2008-11-07 (installing blueman for its
dependencies and then, optionally, uninstalling blueman). Doing this, I
am still using Intrepid and I do backup my phone with Wammu through a
Bluetooth connection with a 2001:f111 D-Link Corp. [hex] DBT-122
Bluetooth adapter.

(By the way: Some messages are about pairing. I think there should be
two different bugs: one on "hardware support regression" and another one
on pairing, for situations without hardware problem other than pairing.
Pairing is a very delicate operation, poorly documented, and maybe
configuration an pin helper files changed with bluez 4 without notice. I
do not know whether there really is a pairing bug or rather a need for
more documentation, explanation and help about pairing but anyway I
think this discussion would be easier if kept separated from hardware
problems. What is the border between the two problems? Maybe whether
hcitool scan detects the phone --or other external Bluetooth device-- or
not. One could add hcitool inq, hcitool info <MAC address> and l2ping
<MAC address> to this test.)

--

Amitiés, Dominique.

Felix Oghină (felix.oghina) wrote :

Can you provide a link? I tried searching meeus-d.be but found nothing.

Dominique Meeùs wrote:
> [...] There is indeed a workaround other than using Hardy: using bluez 3 under Intrepid. This is what I described in my post 2008-11-07 (installing blueman for its dependencies and then, optionally, uninstalling blueman). [...]

Christophe Charlot (c-charlot) wrote :

I just installed bluez 3 ( intalling blueman from the PPA specifief above) :
everyhting is now functional !! :D

Merci beaucoup Dominique !

Dominique Meeùs (dominiquem) wrote :

Znupi a écrit ce qui suit, le 17/11/08 22:07 :
> Can you provide a link? I tried searching meeus-d.be but found nothing.
>
> Dominique Meeùs wrote:
>
>> [...] There is indeed a workaround other than using Hardy: using bluez 3 under Intrepid. This is what I described in my post 2008-11-07 (installing blueman for its dependencies and then, optionally, uninstalling blueman). [...]
>>

Do you mean searching my post in the page #289836? You should then
search "Dominique Meeùs" or "2008-11-07" because e-mail addresses do not
appear explicitly on the page.

If you were searching for my website, then http://meeus-d.be should
do, even if http://www.meeus-d.be is more classical. In the
http://www.meeus-d.be/linux/ folder, there is a Bluetooth page.

--

Amitiés, Dominique.

frausch (rauscher) wrote :

Hi,

same problem on my Lifebook S7010. It has an internal bluetooth/wlan adapter connected via usb. lsusb gives:

Bus 004 Device 005: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth

reinstalling the bluetooth packages does not help. There is no bluetooth icon (kde4) displayed. Bluetooth worked fine with 8.04

Cheers

frausch (rauscher) wrote :

Hi,

for me it seems to be connected to the kde bluetooth service. The bluetooth adapter is recognized by the system, and I can connect to my cellphone using command line tools.

Cheers

Frausch

description: updated
Dominique Meeùs (dominiquem) wrote :

Jonathan Ernst a écrit ce qui suit, le 21/11/08 10:59 :
> ** Description changed:
>
> [...]
>
> == Known workaround ==
> none (besides using Ubuntu Hardy)
> [...]
I don't agree. There is indeed a workaround other than using Hardy:
using bluez 3 under Intrepid. This is what I described in my post
2008-11-07 (install blueman for its dependencies and then, optionally,
uninstall blueman).
--

Amitiés, Dominique.

BrowneR (chris-scotland) wrote :

Dominique,

I have tried your suggestion and installed blueman (and bluez 3) however this did not fix anything for me. If anything it made things worse...

Using blueman I could see my phone but not pair with it. My phone no longer saw the computer at all.

The bluetooth-applet and bluetooth-wizard no longer did anything and didn't even recognize my bluetooth dongle was plugged in any more (eg. when using bluez4 an icon would appear in my tray when i plugged my donge in. when using bluez3 this didnt happen any more.)

Chris

Dominique Meeùs (dominiquem) wrote :

BrowneR a écrit ce qui suit, le 24/11/08 23:52 :
> Dominique,
>
> I have tried your suggestion and installed blueman (and bluez 3) however
> this did not fix anything for me. If anything it made things worse...
>
> Using blueman I could see my phone but not pair with it. My phone no
> longer saw the computer at all.
>
> The bluetooth-applet and bluetooth-wizard no longer did anything and
> didn't even recognize my bluetooth dongle was plugged in any more (eg.
> when using bluez4 an icon would appear in my tray when i plugged my
> donge in. when using bluez3 this didnt happen any more.)
>

Of course some recent applets do not work with an older bluez. (I have
no Bluetooth icon either in the tray. ) I would not rely on applets to
judge whether a device is recognized or not. I am certainly not a
command line fanatic and I prefer GUI apps (when they work). But when
they don't, you have to try some commands to make sure, in this case
"lsusb", "hciconfig" (should show the Mac address and state "Running" --
if it does), "hcitool scan" (should see the phone and give it's Mac
address).

I must confess that I had trouble in pairing. But ultimately it worked.

Anyway, you may have a different situation. I do connect Wammu to my
Nokia 6021 phone through Bluetooth under Intrepid with a "ID 2001:f111
D-Link Corp. [hex] DBT-122 Bluetooth adapter" but I cannot guarantee
that it works for all dongles and all phones on all computers for all
purposes.

--

Amitiés, Dominique.

Stiff (stiff.ru) wrote :

I have resembling bug on ubuntu intrepid with dongle
Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
hcitool scan works, but i can't browse services or connect to them.
sdptool browse xx:xx:xx:xx:xx
Failed to connect to SDP server on xx:xx:xx:xx:xx: Connection timed out

some strings from dmesg when the dongle was plugged in
[ 1758.844077] usb 2-1: new full speed USB device using ohci_hcd and address 2
[ 1769.015274] usb 2-1: configuration #1 chosen from 1 choice
[ 1769.287117] Bluetooth: Generic Bluetooth USB driver ver 0.3
[ 1769.289731] usbcore: registered new interface driver btusb
[ 2037.925061] hci_cmd_task: hci0 command tx timeout

The problem is in kernel 2.6.27, i have installed the old kernel from hardy (2.6.24) and the dongle works fine with it.
Of course, this is regression

Podness (classified51a) wrote :

Installing the old kernel doesn't fix the bluetooth.. Yes some features are back but I still fail on transforming files.

It used to work fine on Hardy and it stopped working when I upgraded to 8.10.

psychok7 (nunok7) wrote :

didnt work for me downgrading bluez.. anymore ideais?

BrowneR (chris-scotland) wrote :

I believe this is a kernel issue so marking it as a duplicate of bug 268502 so it can be addressed by the kernel team.

isecore (isecore) wrote :

For what it's worth, I bought one of these mentioned in the description:

Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Without knowing that it was listed here, and it works flawlessly for me now. No clue why.

Ian M. Stewart (ims) wrote :

I don't know if it will help anyone, but I have the same issues with two different USB Bluetooth dongles. lsusb | grep Blue
shows me
Bus 005 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
and
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Neither is discovered with my standard Ubuntu 8.10 installation.

BTW, both of these dongles are cheap rip-off copies from China, although sourced through reputable suppliers.

maximi89 (maximi89) wrote :

ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
Linux Maximiliano 2.6.29-2-686 #1 SMP Sun May 17 17:56:29 UTC 2009 i686 GNU/Linux
Debian Unstable
Bluez-utils 3.36-3
hcid - HCI daemon ver 3.36

maximi89@Maximiliano:~$ lsmod |grep hci
ohci_hcd 20164 0
ehci_hcd 29936 0
usbcore 124912 8 ohci_hcd,ehci_hcd,usblp,btusb,gspca_sunplus,gspca_main,usbhid
maximi89@Maximiliano:~$ lsmod |grep blue
bluetooth 46052 9 bnep,sco,rfcomm,l2cap,btusb

cat /var/log/daemon.log
May 21 21:41:16 Maximiliano hcid[10457]: HCI dev 0 down
May 21 21:41:16 Maximiliano hcid[10457]: Stopping security manager 0
May 21 21:41:16 Maximiliano hcid[10457]: Device hci0 has been disabled
May 21 21:41:16 Maximiliano hcid[10457]: HCI dev 0 unregistered
May 21 21:41:16 Maximiliano hcid[10457]: Unregister path: /org/bluez/hci0
May 21 21:41:16 Maximiliano hcid[10457]: Device hci0 has been removed
May 21 21:41:18 Maximiliano hcid[10457]: HCI dev 0 registered
May 21 21:41:18 Maximiliano hcid[10457]: HCI dev 0 up
May 21 21:41:18 Maximiliano hcid[10457]: Device hci0 has been added
May 21 21:41:18 Maximiliano hcid[10457]: Starting security manager 0
May 21 21:41:19 Maximiliano hcid[10457]: Can't read version info for hci0: Connection timed out (110)
May 21 21:41:28 Maximiliano hcid[13028]: Can't set link policy on hci0: Connection timed out (110)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers