<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - PulseAudio fails to detect bluetooth speakers"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94056">94056</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>PulseAudio fails to detect bluetooth speakers
</td>
</tr>
<tr>
<th>Product</th>
<td>PulseAudio
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>modules
</td>
</tr>
<tr>
<th>Assignee</th>
<td>pulseaudio-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>stefannagy@fsfe.org
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>pulseaudio-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>lennart@poettering.net
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=121606" name="attach_121606" title="log file (no workaround)">attachment 121606</a> <a href="attachment.cgi?id=121606&action=edit" title="log file (no workaround)">[details]</a></span>
log file (no workaround)
After pairing bluetooth speakers with my notebook I never had any problems
connecting them, but they don't appear in GNOME audio settings (or pavucontrol)
as audio output device.
The first workaround I used for months was to restart bluetoothd before
connecting the speakers – then it worked, after connecting the speakers they
were listed in GNOME audio settings. Several weeks ago I read that this problem
had something to do with GDM capturing the A2DP sink on session start, so to
prevent GDM from doing that I followed a debian wiki entry [1]. This second
workaround was more convenient, now every time I connected my speakers they
were listed in GNOME audio settings immediately. Some days ago I read that it
wasn't necessary to prevent GDM from starting pulseaudio. The only thing I'd
have to do is to prevent module-bluetooth-discover from being started by
default but to start it with X11 [2]. This third workaround works for me too.
As I understand it, the pulseaudio module module-bluetooth-discover is
responsible for detecting available bluetooth audio devices using BlueZ. GDM
starts a pulseaudio process before the user does and module-bluetooth-discover
in fact works - but for the GDM pulseaudio process, not the one that gets
started with X11.
I verified that by connecting my bluetooth speakers in GDM (I can connect my
speakers to the last used paired device by pushing a button). After connecting
the speakers, GDM used them for audio output immediately. After that I started
a GNOME session and my bluetooth speakers were not used as audio output and not
listed in GNOME audio settings as audio output device. When I switched to the
virtual console running GDM my bluetooth speakers were still used for audio
output.
I'll attach three pulseaudio log files: pulse.log is without any workaround,
pulse-workaround2 with the workaround described in the debian wiki [1], and
pulse-workaround3 with the workaround described in <a href="show_bug.cgi?id=94056#c1">Comment 1</a> of the
gnome-bluetooth bug report [2].
[1] <a href="https://wiki.debian.org/BluetoothUser/a2dp#Troubleshooting">https://wiki.debian.org/BluetoothUser/a2dp#Troubleshooting</a>
[2] <a href="https://bugzilla.gnome.org/show_bug.cgi?id=749208#c1">https://bugzilla.gnome.org/show_bug.cgi?id=749208#c1</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>