Comment 20 for bug 554471

Given that;

  - the problem appears to be at a pretty low-level,

  - the only known method of circumvention appears to be to reset the state information held in /var/lib/bluetooth, which is used by the bluez bluetoothd daemon,

  - that bluetoothd is owned by the bluez package, and

  - even the bluez utilities and tools can't remove these corrupted states,

it looks a lot like this is actually a fairly low-level bug with either bluez or the associated utilities, so I'm including the blues package in this bug report.

Julie
x