Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta

Bug #288613 reported by Dave Morley
34
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Confirmed
Medium
Stiff

Bug Description

Binary package hint: gnome-bluetooth

RELEASE: Intrepid
CD/DVD VARIANT: Ubuntu Desktop 32/64 bit cd
ISO BUILD: 20081022

SYMPTOMS: In beta I could pair my phone to my pc with no issues. However now in RC I cannot. I have added the bluez-compat package incase it was anything to do with that and still no pairing. Also rather than taking a couple of seconds to locate my phone it is taking 1-3 minutes. This is a major step backwards.

CAUSE: Unknown

STEPS TO REPRODUCE:
1/ make your phone visible
2/ insert your bluetooth dongle
3/ click on the bluetooth icon
4/ click on setup device and watch as the first 3-4 time it fails to detect your device
5/ final device discovered pairing failed

Revision history for this message
Dave Morley (davmor2) wrote :

Correction to my earlier statement:

It was just after beta when the new look bluetooth-applet was introduced. At that point it was working without any issues.

Revision history for this message
Dave Morley (davmor2) wrote :

tester@tester-desktop:~$ sudo bluetoothd -nd
bluetoothd[5793]: Bluetooth daemon
bluetoothd[5793]: Enabling debug information
bluetoothd[5793]: parsing main.conf
bluetoothd[5793]: offmode=NoScan
bluetoothd[5793]: discovto=0
bluetoothd[5793]: pageto=8192
bluetoothd[5793]: name=%h-%d
bluetoothd[5793]: class=0x000100
bluetoothd[5793]: inqmode=0
bluetoothd[5793]: Starting SDP server
bluetoothd[5793]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[5793]: /usr/lib/bluetooth/plugins/input.so
bluetoothd[5793]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[5793]: /usr/lib/bluetooth/plugins/audio.so
bluetoothd[5793]: Unix socket created: 11
bluetoothd[5793]: Telephony plugin initialized
bluetoothd[5793]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[5793]: /usr/lib/bluetooth/plugins/serial.so
bluetoothd[5793]: /usr/lib/bluetooth/plugins/service.so
bluetoothd[5793]: /usr/lib/bluetooth/plugins/netlink.so
bluetoothd[5793]: Starting experimental netlink support
bluetoothd[5793]: Failed to find Bluetooth netlink family
bluetoothd[5793]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
bluetoothd[5793]: /usr/lib/bluetooth/plugins/hal.so
bluetoothd[5793]: /usr/lib/bluetooth/plugins/network.so
bluetoothd[5793]: /etc/bluetooth/network.conf: Key file does not have key 'Disable'
bluetoothd[5793]: /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[5793]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[5793]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[5793]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[5793]: Config options: InterfacePrefix=bnep%d, PANU_Script=avahi-autoipd, GN_Script=avahi-autoipd, NAP_Script=dhclient, GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[5793]: bridge pan0 created
bluetoothd[5793]: HCI dev 0 registered
bluetoothd[5793]: child 5795 forked
bluetoothd[5793]: HCI dev 0 already up
bluetoothd[5793]: Can't read version info for /org/bluez/hci0: Connection timed out (110)
bluetoothd[5793]: Starting security manager 0
bluetoothd[5793]: Agent registered for hci0 at :1.29:/org/bluez/agent/hci0
bluetoothd[5795]: Can't set link policy on hci0: Connection timed out (110)
bluetoothd[5793]: child 5795 exited

Revision history for this message
Emmet Hikory (persia) wrote :

Pairing was succesful with bluez 4.12-0ubuntu2 and failed with 4.12-0ubuntu4. In both cases using bluez-gnome 1.8-0ubuntu1.

Changed in bluez-gnome:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Mario Limonciello (superm1) wrote :

Well that's awfully odd... to narrow this down ever further, 4.12-0ubuntu3, could you grab that and see that it works or doesn't?

Revision history for this message
Dave Morley (davmor2) wrote :

It didn't work for me when I tried backtracking from ubuntu4.

Revision history for this message
VladimirCZ (vlabla) wrote :

I have similar problem. I cannot connect to my Nokia phones 6021 a 6310i and browse their content.

My USB bluetooth adapter worked well under Hardy.

Under 8.10 final release (to be exact it is a fully updated installation starting from the 8.10 beta version):
works: the Bluetooth manger can detect connectible devices in neighborhood and I can pair them to my PC
does not work: I cannot connect to the paired mobiles -> I cannot browse their content and there are also no icons of mounted mobile phones on my desktop and in the media folder of Nautilus.

USB bluetooth adapter:
Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

OS Ubuntu 8.10 beta 64-bit (2.6.27-7-generic)
Motherboard Asus P5KPL (Intel chipset with Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GH)

Revision history for this message
Louis-Dominique Dubeau (ldd) wrote :

I also tried reverting to 4.12-0ubuntu2 and it did not work.

Emmet, did you get the old binaries for 4.12-0ubuntu2 from the repository? Or did you recompile 4.12-0ubuntu2 yourself?

Revision history for this message
kylea (kylea) wrote :

I can ditto all these comments - beta Bluetooth worked fairly well, but since RC nothing works. I have a Nokia 6233 and a Dell E6500.

Revision history for this message
kylea (kylea) wrote :

kylea@kylea-e6500:~$ bluetoothd -nd

bluetoothd[18532]: Bluetooth daemon
bluetoothd[18532]: Enabling debug information
bluetoothd[18532]: parsing main.conf
bluetoothd[18532]: offmode=NoScan
bluetoothd[18532]: discovto=0
bluetoothd[18532]: pageto=8192
bluetoothd[18532]: name=%h-%d
bluetoothd[18532]: class=0x000100
bluetoothd[18532]: inqmode=0
bluetoothd[18532]: Unable to get on D-Bus

Revision history for this message
kylea (kylea) wrote :

Has there been any movement with this?

Any chance bluetooth will work soon?

Revision history for this message
BrowneR (chris-scotland) wrote :
Download full text (19.0 KiB)

This also effects me. After upgrade from Hardy I can no longer pair with my phone, use it as an HID remote or transfer files.

Trying to pair with phone using bluetooth-wizard:

chris@chris-laptop:~$ sudo bluetoothd -nd
bluetoothd[11216]: Bluetooth daemon
bluetoothd[11216]: Enabling debug information
bluetoothd[11216]: parsing main.conf
bluetoothd[11216]: offmode=NoScan
bluetoothd[11216]: discovto=0
bluetoothd[11216]: pageto=8192
bluetoothd[11216]: name=%h-%d
bluetoothd[11216]: class=0x000100
bluetoothd[11216]: inqmode=0
bluetoothd[11216]: Starting SDP server
bluetoothd[11216]: Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[11216]: /usr/lib/bluetooth/plugins/netlink.so
bluetoothd[11216]: Starting experimental netlink support
bluetoothd[11216]: Failed to find Bluetooth netlink family
bluetoothd[11216]: Can't init plugin /usr/lib/bluetooth/plugins/netlink.so
bluetoothd[11216]: /usr/lib/bluetooth/plugins/hal.so
bluetoothd[11216]: /usr/lib/bluetooth/plugins/input.so
bluetoothd[11216]: input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[11216]: /usr/lib/bluetooth/plugins/network.so
bluetoothd[11216]: /etc/bluetooth/network.conf: Key file does not have key 'Disable'
bluetoothd[11216]: /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[11216]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[11216]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[11216]: /etc/bluetooth/network.conf: Key file does not have key 'Interface'
bluetoothd[11216]: Config options: InterfacePrefix=bnep%d, PANU_Script=avahi-autoipd, GN_Script=avahi-autoipd, NAP_Script=dhclient, GN_Interface=pan0, NAP_Interface=pan1, Security=true
bluetoothd[11216]: bridge pan0 created
bluetoothd[11216]: /usr/lib/bluetooth/plugins/serial.so
bluetoothd[11216]: /usr/lib/bluetooth/plugins/audio.so
bluetoothd[11216]: Unix socket created: 13
bluetoothd[11216]: Telephony plugin initialized
bluetoothd[11216]: HFP AG features: "Ability to reject a call" "Enhanced call status" "Extended Error Result Codes"
bluetoothd[11216]: /usr/lib/bluetooth/plugins/service.so
bluetoothd[11216]: HCI dev 0 registered
bluetoothd[11216]: child 11218 forked
bluetoothd[11216]: HCI dev 0 already up
bluetoothd[11216]: network_server_probe: path /org/bluez/hci0
bluetoothd[11216]: Adding record with handle 0x10000
bluetoothd[11216]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[11216]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[11216]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[11216]: Record pattern UUID 00001115-0000-1000-8000-00805f9
bluetoothd[11216]: register_server_record: got record id 0x10000
bluetoothd[11216]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
bluetoothd[11216]: network_server_probe: path /org/bluez/hci0
bluetoothd[11216]: Adding record with handle 0x10001
bluetoothd[11216]: Record pattern UUID 0000000f-0000-1000-8000-00805f9
bluetoothd[11216]: Record pattern UUID 00000100-0000-1000-8000-00805f9
bluetoothd[11216]: Record pattern UUID 00001002-0000-1000-8000-00805f9
bluetoothd[11216]: Record pattern UUID 00001117-0000...

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :

I'm unable to connect to PAN on my mobile phone (Sony-Ericsson K850i) with the 2.6.27 kernels, but I was able to do so with Hardy's 2.6.24 kernel. I don't do file transfers, only PAN.

To be precise about the kernels: I ran Hardy the distro for a while with Intrepid beta kernels (to test the kernels), and connections made with "pand" were ultimately rejected with "Connection Refused" when running those Intrepid kernels (on a Hardy distro), but when booting a Hardy kernel "pand" worked fine.

It's a bit odd, in that the connection seems to work at first, with the phone's screen asking if it's ok to accept this connection. But on saying ok, then the phone asks a _second_ time the same question, and when it _asks_ the second time, "pand" reports "Connection Refused" immediately. Note that the laptop and phone are already known to each other, this is just the phone asking "Laptop wants to use the phone as a modem? yes or no". If I tell the phone to allow it without asking, there are no dialogs or delays, "pand" just gets to "Connection Refused" very quickly.)

Whereas with Hardy's own kernel, the phone asks just once, and the connection always succeeds in "pand"'s log.

Note the bluetooth userspace utilities were _exactly_ the same in these tests. So in my case, the ability to pair with the phone was affected by booting a different kernel *alone*, with 2.6.27 kernels failing and 2.6.24 kernels succeeding.

I'm now running Intrepid the whole distro (upgraded from Hardy), and generally up to date. The ability to pair (with "pand") is still broken, same as running Hardy with Intrepid's kernel. I haven't yet had a chance to try the other way around and boot the Hardy kernel on my Intrepid distro, to see if that fixes "pand".

So for people with pairing problems, it might be worth booting Hardy's latest kernel, to see if that fixes the problem. If it does, that will at least narrow it down to the kernel bluetooth stack. I suspect there's more than one different pairing problem, but this is one of them.

Revision history for this message
Stiff (stiff.ru) wrote :

The bug there is, ubuntu 8.10 with latest updates, on laptop dell inspiron 1501 with external usb dongle.
Bus 002 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
i only can search devices, but i can't pair my phone or connect file transfer or rfcomm.
but if i search devices on telephone, i can pair them, requesting authentification from telephone.

Changed in bluez:
assignee: nobody → stiff11
Revision history for this message
Ben Tobin (tbone-drclabs) wrote :

I've been playing with it, and it seems like it's not even properly initiating the connection while it claims to be trying to pair the devices. The reason I think so is that if you tell it to pair to a device, then while it's waiting, you go to a command line and tell it to connect manually with "sudo hcitool cc 00:00:00:00:00:00" (using the proper ID for your device) the pairing window will move on to the next step and finish pairing the devices.

Even after pairing, I have similar issues with using a bluetooth headset with my computer. Every time it needs to start sending audio, it will time out unless I give it a boost with a command-line connect.

Revision history for this message
okkie (okkiel) wrote :

From what I've read till now I think the whole Intrepid bluetooth problem has been reported in full as it appears that pairing the devices is the main issue.
What is of major importance to me and many others i'm sure, is the time it will take to fix the problem as my income depend on transferring files to and from my phone.I lack the knowledge to offer any personal help and would like to thank the programmers in advance for their efforts to rectify the problem as soon as possible.

Revision history for this message
kylea (kylea) wrote :

okkie - I can pair nearly at will - but what happensto me is that the bluetooth connection will not "stick". I have been getting intermittent syncing and file file transferring to work for two days then it stops for a 3 or 4 and then it will work for 8 hours and then stop.

Here is a log from the last week

1/12/2008 21:45 | kyle Amadio
      Nope that does not seem to make any difference.
      Can send files between my phone and wifes.

01/12/2008 21:37 | kyle Amadio
      Monday morning 1/12/2008 - went to work, started PC - interestingly the Dell Bluetooth switch was not on.
      Noticed this well after the PC had booted. Turned on the switch and the sync process and other Bluetooth functions worked.
     Have now returned home and 5 hours after leaving work. Bluetooth has stopped working.
     Will see if the Dell bluetooth switch being off make during the boot process makes any difference.

30/11/2008 21:03 | kyle Amadio
     Ok its Sunday 30th still not syncing - have tried a variety of things, resetting phone, re-pairing, restarting PC bluetooth.
     I can send images and music files between my 6233 and my wifes successfully, both ways.

29/11/2008 08:07 | kyle Amadio
    Shutdown - went to bed - 8 hours later - it works.
    Changed nothing on the phone

28/11/2008 22:48 | kyle Amadio
    Ok - did a shutdown and reboot. Syncing / Bluetooth stopped working.

28/11/2008 22:36 | kyle Amadio
       Well- went home and syncing is all good again.

28/11/2008 12:15 | kyle Amadio
      Syncing worked fine for two days - failed this morning (Fri 28th).

Revision history for this message
Jamie Lokier (jamie-shareable) wrote : Re: [Bug 288613] Re: Intrepid: RC Regression. Bluetooth no longer pairs correctly which it did in beta

okkie wrote:
> >From what I've read till now I think the whole Intrepid bluetooth problem has been reported in full as it appears that pairing the devices is the main issue.
> What is of major importance to me and many others i'm sure, is the time it will take to fix the problem as my income depend on transferring files to and from my phone.I lack the knowledge to offer any personal help and would like to thank the programmers in advance for their efforts to rectify the problem as soon as possible.

I boot a 2.6.24 kernel from Hardy, and then Bluetooth works fine for me.

I have these packages from Ubuntu Hardy (8.04) installed on my
Intrepid system:

    linux-image-2.6.24-21-generic (version 2.6.24-21.43)
    linux-restricted-modules-2.6.24-21-generic (version 2.6.24.14-21.51)
    linux-ubuntu-modules-2.6.24-21-generic (version 2.6.24-21.33)
    linux-backports-modules-2.6.24-21-generic (version 2.6.24-21.27)

With those packages, Linux 2.6.24-21 is available in the boot menu.

To be able to install those packages, I have these two lines added to
the end of /etc/apt/sources.list:

    deb http://archive.ubuntu.com/ubuntu/ hardy main restricted
    deb http://archive.ubuntu.com/ubuntu/ hardy-updates main restricted

Then those packages can be selected for install in Synaptic.

Note that they won't upgrade to newer Hardy kernel packages
automatically. Indeed, while writing this I just noticed there are
2.6.24-22 versions out, which I'm about to select and install. :-)

-- Jamie

Revision history for this message
BrowneR (chris-scotland) wrote :
Revision history for this message
kylea (kylea) wrote :

Ok : here is what I think is going: (I have a Dell E6500 laptop)

IF I have my Bluetooth radio switch turned OFF during the Boot Up process and only turn it ON AFTER Gnome is fully loaded and all processes are finished THEN Bluetooth processes work.

Have proven this with repeated tests:

IF the Bluetooth radio switch is ON during the boot up then Bluetooth will not work.

SO what is going on - surely this is enough for you guys to make a search now. Can we change the load sequence of the Bluetooth daemon to load last ?

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :

I've used all combinations of Hardy/Intrepid kernels, and Hardy/Intrepid bluez packages.

The probles I've had are entirely dependent on kernel version, and the bluez version makes no difference at all (that I've found).

Therefore I think this bug should be marked as a duplicate of #268502, which is the same bug but assigned to the kernel and Ubuntu Kernel Team. The kernel is the place to look for this one.

The problems I've observed are dependent on kernel version, and not dependent at all on bluez version (I've used all combinations.Because the problem is highly dependent on kernel ver

Revision history for this message
BrowneR (chris-scotland) wrote :

I agree Jamie, marked as such.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.