Comment 299 for bug 268502

I just tried the bluez 4.32 downgrade workaround on Ubuntu 10.10 and the basics work ok with Blueman but I hit a serious issue:

Dec 21 21:14:21 linux bluetoothd[1375]: link_key_request (sba=00:22:43:D3:50:4D, dba=00:23:7F:81:DC:01)
Dec 21 21:14:21 linux bluetoothd[1375]: link_key_request (sba=00:22:43:D3:50:4D, dba=00:23:7F:81:DC:01)
Dec 21 21:14:22 linux pulseaudio[1919]: module-bluetooth-device.c: 00:23:7F:81:DC:01 is not known.
Dec 21 21:14:22 linux pulseaudio[1919]: module.c: Failed to load module "module-bluetooth-device" (argument: "address=00:23:7F:81:DC:01 profile=hsp sink_properties=device.icon_name=blueman card_properties=device.icon_name=blueman"): initialization failed.
Dec 21 21:14:22 linux bluetoothd[1375]: Badly formated or unrecognized command: AT+PLTWB=4
Dec 21 21:14:22 linux bluetoothd[1375]: Badly formated or unrecognized command: AT+PLTWN=1

Blueman's PulseAudio.py reports failure to load "module-bluetooth-device" (python call to C lib string). So no audio is possible but device is discovered ok.

I'm using Plantronics Voyager Pro perhaps that is contributing to this workaround not being successful but FYI. I'm going to attempt installing the latest build of bluez next.