<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Bluetooth headset stops working after pulseaudio update to 11"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102660#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Bluetooth headset stops working after pulseaudio update to 11"
href="https://bugs.freedesktop.org/show_bug.cgi?id=102660">bug 102660</a>
from <span class="vcard"><a class="email" href="mailto:mwilck@suse.de" title="Martin Wilck <mwilck@suse.de>"> <span class="fn">Martin Wilck</span></a>
</span></b>
<pre>(In reply to Arun Raghavan from <a href="show_bug.cgi?id=102660#c4">comment #4</a>)
<span class="quote">> What would help here is (a) logs from bluez and PA when things aren't
> working, and (b) if you're feeling adventurous, since you've got the code
> from git built and running, a git bisect taking us to the problematic commit.</span >
Thanks for looking into this! I attached the PA logs above. Didn't look into
the bluez logging configuration so far. Bisecting was my plan but it was
difficult because of the problems with reproduction (<a href="show_bug.cgi?id=102660#c3">comment #3</a>). Bisection
requires a reliable "good/bad" distinction.
Anyway, you seem to have spotted the problem already, many thanks.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>