Comment 295 for bug 268502

I just tried the above workaround that I posted (going back to bluez-4.32) on plain Maverick amd64 (actually a Kubuntu 10.10 installation) and it did work (which was not working earlier with the same timeout problem). On Kubuntu, since bluedevil does not have any dependencies with bluez -- unlike gnome-bluetooth, downgrading bluez and testing was very easy.

@Matt - Make sure you remove the module, stop bluetooth service, remove the device - downgrade bluez and put everything back. Or simply reboot and check.