https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/386224 ->
"I had the same issue, Its resolved by choosing a 2.6.28 kernel from the grub menu. The rpoblem was with 2.6.31, havnt tried 2.6.30.
Same result with bluez 4.45 from ubuntu, and 4.46 from bluez git. (havnt patched kernel or anything silly like that yet, maybee try that if not much movement here)"
It seems this is a kernel related bug, the person in cause ( https://bugs.launchpad.net/~scarletpimpernal )said that the problem it's solved with 2.6.28 kernel ?!
It could simply be a new way in wich bluetooth devices are adressed?
https:/ /bugs.launchpad .net/ubuntu/ +source/ bluez/+ bug/386224 ->
"I had the same issue, Its resolved by choosing a 2.6.28 kernel from the grub menu. The rpoblem was with 2.6.31, havnt tried 2.6.30.
Same result with bluez 4.45 from ubuntu, and 4.46 from bluez git. (havnt patched kernel or anything silly like that yet, maybee try that if not much movement here)"
It seems this is a kernel related bug, the person in cause ( https:/ /bugs.launchpad .net/~scarletpi mpernal )said that the problem it's solved with 2.6.28 kernel ?!
It could simply be a new way in wich bluetooth devices are adressed?