Comment 3 for bug 211157

I just encountered this same kind of lockup today. I have tried 2 different phones in combination with 2 different bluetooth adapters. The lockup only occurs on one of the phones, the HTC Tilt - AT&T 8925 (Win Mobile). The Sony Ericsson (Symbian) phone does not have this problem.

When I initiate bonding from the desktop, no problems. Can connect and browse the device. When I initiate bonding from the HTC Tilt, the system immediately and complete freezes everything.

I tried to catch an error message. I left open two terminal windows, one tailing /var/log/messages and the other tailing /var/log/dmesg and I initiated bonding from the HTC Tilt. It bonded then locked and there were no log messages issued. And when I reboot. There is no record of any errors that I can find.

It doesn't matter what preferences or services I have enabled on the Bluetooth Applet (0.25) the result is the same.

Using Ubuntu Hardy 8.04, kernel 2.6.24-16-generic, gnome 2.22.1 with all latest patches on Athlon machine with 512 MB RAM (non-descript e-machine).

Bluetooth devices: no-name class 1 device and IOgear gbu221 (class 2).

Phones: HTC Tilt - AT&T 8925 (Win Mobile) <- the problem phone and Sony Ericsson (Symbian) <- the no problem phone.

This is NOT a random lockup. It happens every single time I initiate bonding from the HTC Tilt and the lockup occurs immediately after "bonding completed" message displays.