[Bug 329828] [NEW] Bluetooth/Bluez 4.xx unable to use some adapters

[Dominique Meeùs]

Public bug reported:

Binary package hint: bluetooth

I suspect this is a bluetooth/bluez/bluetoothd bug, NOT a kernel bug
because my Bluetooth adapter DOES work with kernel 2.6.28 and
bluetooth/bluez 3.xx hcid (see
https://bugs.launchpad.net/ubuntu/+bug/289836/comments/19 for Intrepid
with kernel 2.6.27 and below for Jaunty).

I know most bluetooth bugs are marked as duplicate of a kernel bug. I
file this as a separate bug on purpose.

I am working in Jaunty :~$ lsb_release -rd
Description:	Ubuntu jaunty (development branch)
Release:	9.04
Kernel :~$ uname -r
2.6.28-7-generic
with bluetooth/bluez 4.29: ~$ dpkg -l blue*
||/ Nom            Version        Description
+++-==============-==============-============================================
ii  bluefish       1.0.7-5        advanced Gtk+ HTML editor
ii  bluetooth      4.29-0ubuntu1  Bluetooth support
ii  bluez          4.29-0ubuntu1  Bluetooth tools and daemons
ii  bluez-alsa     4.29-0ubuntu1  Bluetooth audio support
ii  bluez-cups     4.29-0ubuntu1  Bluetooth printer driver for CUPS
ii  bluez-gnome    1.8-0ubuntu2   Bluetooth utilities for GNOME
ii  bluez-gstreame 4.29-0ubuntu1  Bluetooth gstreamer support
ii  bluez-utils    4.29-0ubuntu1  Transitional package
also
ii  gnome-bluetoot 0.11.0-0ubuntu GNOME Bluetooth tools.
ii  libbluetooth3  4.29-0ubuntu1  Library to use the BlueZ Linux Bluetooth sta

This is my D-Link adapter: ~$ lsusb | grep Bluetooth
Bus 001 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

It is recognised: hcitool dev
Devices:
	hci0	00:13:46:00:55:A0

and active: ~$ hciconfig
hci0:	Type: USB
	BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
	UP RUNNING 
	RX bytes:667 acl:0 sco:0 events:19 errors:0
	TX bytes:373 acl:0 sco:0 commands:29 errors:0

though it doesn't see my phone (which is Bluetooth "visible"): ~$ hcitool scan
Scanning ...
Inquiry failed: Connection timed out
and: ~$ hcitool inq
Inquiring ...
Inquiry failed.: Connection timed out

even if given the BD address: ~$ sudo hcitool info 00:13:70:0E:8A:77
Requesting information ...
Can't create connection: Connection timed out

==============

Replacing bluetooth/bluez 4.29 by bluetooth/bluez 4.30: ~$ dpkg -l *blue*
||/ Nom            Version        Description
+++-==============-==============-============================================
ii  bluefish       1.0.7-5        advanced Gtk+ HTML editor
ii  bluetooth      4.30-0ubuntu1~ Bluetooth support
ii  bluez          4.30-0ubuntu1~ Bluetooth tools and daemons
ii  bluez-gnome    1.8-0ubuntu2   Bluetooth utilities for GNOME
ii  gnome-bluetoot 0.11.0-0ubuntu GNOME Bluetooth tools.
ii  libbluetooth3  4.30-0ubuntu1~ Library to use the BlueZ Linux Bluetooth sta
ii  python-bluez   0.15-1.1       Python wrappers around BlueZ for rapid bluet

it still doesn't work: hcitool scan
Scanning ...
Inquiry failed: Connection timed out

==============

Replacing bluetooth/bluez 4.29 by bluetooth/bluez 3.36: ~$ dpkg -l *blue*
||/ Nom            Version        Description
+++-==============-==============-============================================
ii  bluetooth3     3.26-0ubuntu14 Bluetooth stack utilities
ii  bluez3-audio   3.26-0ubuntu14 Bluetooth audio support
ii  bluez3-utils   3.26-0ubuntu14 Bluetooth tools and daemons
ii  gnome-bluetoot 0.11.0-0ubuntu GNOME Bluetooth tools.
ii  libbluetooth2  3.29-0ubuntu1  Library to use the BlueZ Linux Bluetooth sta
ii  libbluetooth3  4.30-0ubuntu1~ Library to use the BlueZ Linux Bluetooth sta
ii  python-bluez   0.15-1.1       Python wrappers around BlueZ for rapid bluet

Adapter is active: ~$ hciconfig
hci0:	Type: USB
	BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
	UP RUNNING 
	RX bytes:667 acl:0 sco:0 events:19 errors:0
	TX bytes:669 acl:0 sco:0 commands:38 errors:0

it still doesn't work: hcitool scan
Scanning ...
Inquiry failed: Connection timed out

OK. Let's try to restart

==============

Upon restart, hci0 was down: ~$ 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

but i could activate it:: ~$ sudo hciconfig hci0 up
successfully: ~$ hciconfig
hci0:	Type: USB
	BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
	UP RUNNING PSCAN ISCAN 
	RX bytes:937 acl:0 sco:0 events:22 errors:0
	TX bytes:332 acl:0 sco:0 commands:22 errors:0

and not only my phone was found: :~$ sudo hcitool scan
Scanning ...
	00:13:70:0E:8A:77	Nokia 6021

but also Wammu did connect and I could successfully backup my phone as a
Wammu backup file and in particular my calendar as an ics file that I
did import successfully within the Lightning extension of Thunderbird.

In short: I DID use successfully a D-Link DBT-122 Bluetooth adapter,
with kernel 2.6.28

I am sorry that I forgot to look at the daemon log at each try. I give
some typical excerpts of the daemon log in attachment, with bluetoothd
errors and the final success of hcid.

** Affects: bluez (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Bluetooth/Bluez 4.xx unable to use some adapters
https://bugs.launchpad.net/bugs/329828
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in ubuntu.