Dell BT Travel mouse not pairing

[Ken Pratt]

Under Jaunty 9.04 Beta x86_64 desktop edition, I can not pair my "Dell BT Travel Mouse". It is found but when I attempt to pair, the bluetooth applet reports that paring failed. I have paired many bluetooth mice successfully - including the Dell non-travel-full-size BT mouse. There is something particular to the travel mouse that breaks.

[Kristoffer Grönlund (kegie)]

I have this same mouse and the same problem on Jaunty 9.04 final.
No matter what I do, the mouse will not pair. I am pretty sure I had it working (not stable though) on a previous version, so there has been a regression of some sort. The mouse is detected and the bluetooth adapter interface claims, after a long while, to have paired successfully. This, however is not true, since the mouse remains in the configuration state even after the applet claims to be finished (I suspect there is a timeout somewhere lower in the bluetooth stack which is not correctly handled in the applet).

I've tried various workarounds, but nothing has been successful.

There is nothing interesting in dmesg beyond the following:

[ 431.005765] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1078.788117] CE: hpet increasing min_delta_ns to 15000 nsec
[ 1390.703686] usb 3-1.2: usbfs: process 6435 (hid2hci) did not claim interface 0 before use
[ 3836.483126] usb 3-1.2: usbfs: process 10289 (hid2hci) did not claim interface 0 before use
[ 4801.840235] CE: hpet increasing min_delta_ns to 22500 nsec
[18541.912365] CE: hpet increasing min_delta_ns to 33750 nsec
[18572.912367] CE: hpet increasing min_delta_ns to 50624 nsec
[20054.920239] CE: hpet increasing min_delta_ns to 75936 nsec
[20056.920211] CE: hpet increasing min_delta_ns to 113904 nsec

Using blueman, I get the following log messages when I try to pair with the mouse (it never leaves discovery state, and the pairing fails):

RequestPinCode (/usr/lib/python2.6/dist-packages/blueman/main/applet/BluezAgent.py:254)
Agent.RequestPinCode
_________
Release (/usr/lib/python2.6/dist-packages/blueman/main/applet/BluezAgent.py:148)
Release
_________
Cancel (/usr/lib/python2.6/dist-packages/blueman/main/applet/BluezAgent.py:155)
cancelled
_________
__del__ (/usr/lib/python2.6/dist-packages/blueman/main/applet/BluezAgent.py:145)
Agent on path /org/blueman/agent/temp/000761D47633 deleted

[Kristoffer Grönlund (kegie)]

Some further information:
~ $ sudo hidd --search
Searching ...
 Connecting to device 00:07:61:D4:76:33
Can't get device information: Software caused connection abort

[Ulisses Furquim (ulissesf)]

Hi Kristoffer, could you capture an hcidump log when the pairing fails, please? You can do that by running 'hcidump -X -V' as root before you try to pair with your mouse. Thank you.

[Kristoffer Grönlund (kegie)]

Dump attached.

I tried running the Karmic alpha 2 live CD. There it worked perfectly, straight away. So it seems to be a solved problem in later versions of bluez.

[Kristoffer Grönlund (kegie)]

Another update: I now updated my Jaunty installation to Karmic (latest from repos) - still have the same problem! So, running from the live CD the mouse paired successfully, but installed it still fails to leave discovery mode. Could there be something strange about my installation? I can't figure out what that might be, though.

[Ulisses Furquim (ulissesf)]

Have you paired the mouse using the live CD? I'm wondering if it wasn't on HID mode and that would be the reason it worked.

[lrkwz (luca-orlandi)]

Same problem with 10.10, the mice was working a few days ago.

~> uname -a
Linux Precision-M4500 2.6.35-23-generic-pae #41-Ubuntu SMP Wed Nov 24 10:35:46 UTC 2010 i686 GNU/Linux

~> sudo hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 00:07:61:E8:D6:DD ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 12 bdaddr 00:07:61:E8:D6:DD type ACL encrypt 0x00
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 12
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 12
    Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
< ACL data: handle 12 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:07:61:E8:D6:DD mode 2 clkoffset 0x0000
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Remote Name Req Complete (0x07) plen 255
    status 0x00 bdaddr 00:07:61:E8:D6:DD name 'Dell BT Travel Mouse'
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 12 packets 1
< ACL data: handle 12 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 12 packets 1
< ACL data: handle 12 flags 0x02 dlen 12
    L2CAP(s): Connect req: psm 1 scid 0x0040
> HCI Event: Number of Completed Packets (0x13) plen 5
    handle 12 packets 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 12 reason 0x16
    Reason: Connection Terminated by Local Host

[lrkwz (luca-orlandi)]

working again after bios update ...

~> sudo firmwaretool --inventory
Wait while we inventory system:
System inventory:
 System BIOS for Precision M4500 = A06

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.