Because this error message happens all the time it's going to happen at the same time as other Bluetooth problems. So people will *think* it's related to those other problems because both occur concurrently in the log.
However because we already know this error message happens on healthy machines with no Bluetooth problems we believe that it's just a coincidence both issues happen concurrently, and that any actual problems should be reported as separate bugs.
I don't think so.
Because this error message happens all the time it's going to happen at the same time as other Bluetooth problems. So people will *think* it's related to those other problems because both occur concurrently in the log.
However because we already know this error message happens on healthy machines with no Bluetooth problems we believe that it's just a coincidence both issues happen concurrently, and that any actual problems should be reported as separate bugs.