Comment 135 for bug 405294

@Daniel, please understand that this is not personal, and I know this is not the right place for such a discussion, but where else ?

This problem is really annoying in 2017, 8 years after the bug was first reported, in a world where bluetooth speakers are of everyday use.

I know this bug has been reported here but also under various Linux subsystem. Googling it returns a massive amount of results each one slightly different from the other, some with workaround, including from the pulseaudio documentation (yes, I read it, tried, made things worse).

Basically this means that the root cause may not have been found yet.

Asking end users to report again and again the same bug in different ways just makes it more difficult for the developers to understand and ultimately correct.

I am fairly sure that 100 people declaring here to be affected by this bug, means that a lot more are too. Maybe only 1 user out of 10 knows how to report it. So the real amount is probably way higher.

@Daniel if you have any influence in this, please try to forward this problem to whomever is able to fix it, it would be very much appreciated.

Best regards,