Bug#998220: pipewire: libspa-0.2-bluetooth not installed

Luc Maisonobe

unread,

Nov 1, 2021, 5:30:04 AM11/1/21

to

Package: pipewire
Version: 0.3.39-3
Severity: normal

Dear Maintainer,

Since upgrade to 0.3.39-3, my Sony WH-1000XM4 doesn't work anymore. It worked
flawlessly a few days ago.

The first problem was that the headset disconnected immediately after
connecting. There was an associated error in journalctl :

src/service.c:btd_service_connect() a2dp-sink profile connect failed for <some
hex numbers> Protocol not available

Some search engine pointed to me that this may be associated with missing
libspa-0.2-bluetooth, so I installed it and this first error disappeared. So a
first suggestion would be to make sure that libspa-0.2-bluetooth is added as a
dependency to some of the pipewire set.

This however did not solve my problem, I will file another bug report for the
remaining part

-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.14.0-2-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pipewire depends on:
ii init-system-helpers 1.60
ii libpipewire-0.3-modules 0.3.39-3
ii pipewire-bin 0.3.39-3

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information

Ralf Jung

unread,

Nov 3, 2021, 10:00:03 PM11/3/21

to

Hi all,

> The first problem was that the headset disconnected immediately after
> connecting. There was an associated error in journalctl :
>
> src/service.c:btd_service_connect() a2dp-sink profile connect failed for <some
> hex numbers> Protocol not available
>
> Some search engine pointed to me that this may be associated with missing
> libspa-0.2-bluetooth, so I installed it and this first error disappeared. So a
> first suggestion would be to make sure that libspa-0.2-bluetooth is added as a
> dependency to some of the pipewire set.

I am having the same problem. According to
https://wiki.debian.org/BluetoothUser/a2dp, one also has to uninstall
pulseaudio-module-bluetooth.

This is one of the rare cases where upgrading Debian just silently broke the
system -- all bluetooth audio functionality just stopped working without
warning. I hope something can be done to avoid this.

Amusingly, the description of the libspa package says " It is considered to be
experimental, and is disabled by default (even if installed) to avoid conflicts
with equivalent functionality in PulseAudio. " -- however, since upgrades now
seem to automatically switch people over from PA to pipewire, does this still
make sense? So far certainly one cannot speak of "equivalent functionality",
since the bluetooth support in PA actually worked out of the box without any
fiddling...

> This however did not solve my problem, I will file another bug report for the
> remaining part

I am also still struggling with getting BT working again; do you have a link to
the other bug report?

Kind regards,
Ralf

Ralf Jung

unread,

Nov 3, 2021, 10:10:03 PM11/3/21

to

>> This however did not solve my problem, I will file another bug report for the
>> remaining part
>
> I am also still struggling with getting BT working again; do you have a link to
> the other bug report?

Addendum: the missing bit in my case (besides installing libspa-0.2-bluetooth
package and removing pulseaudio-module-bluetooth) was that I had to re-pair the
device. Now it seems things are working again as before.

Kind regards,
Ralf

Luc Maisonobe

unread,

Nov 4, 2021, 3:40:03 AM11/4/21

to

Le mercredi 03 novembre 2021 à 21:44 -0400, Ralf Jung a écrit :
>
>
> I am also still struggling with getting BT working again; do you have a
> link to
> the other bug report?

The other bug report is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998221

Michael Biebl

unread,

Nov 4, 2021, 5:10:04 AM11/4/21

to

On 04.11.21 02:44, Ralf Jung wrote:

> This is one of the rare cases where upgrading Debian just silently broke
> the system -- all bluetooth audio functionality just stopped working
> without warning. I hope something can be done to avoid this.
>
> Amusingly, the description of the libspa package says " It is considered
> to be experimental, and is disabled by default (even if installed) to
> avoid conflicts with equivalent functionality in PulseAudio. " --
> however, since upgrades now seem to automatically switch people over
> from PA to pipewire,

I don't think this is true at least I don't see any dependency changes
in Debian which would automatically install pipewire-pulse.

OpenPGP_signature

Luc Maisonobe

unread,

Nov 4, 2021, 5:50:04 AM11/4/21

to

Le jeudi 04 novembre 2021 à 10:01 +0100, Michael Biebl a écrit :
>
>
> I don't think this is true at least I don't see any dependency
> changes
> in Debian which would automatically install pipewire-pulse.

Well, I am using Debian testing, and did not change anything
by myself. It just happened to me that my headset did not work
anymore at one time, and only after lots of search I found that
pipewire (which was unknown to me), was installed and this was
related to the problems.

For now, my headset does not work at all, and I don't know how to fix
it.

Luc

Dylan Aïssi

unread,

Nov 4, 2021, 6:10:04 AM11/4/21

to

Le jeu. 4 nov. 2021 à 10:03, Michael Biebl <bi...@debian.org> a écrit :
>
> I don't think this is true at least I don't see any dependency changes
> in Debian which would automatically install pipewire-pulse.

In fact, when I changed the order of wireplumber and
pipewire-media-session in the recommends field of pipewire-bin (as
recommended by pipewire devs) that caused the installation of
wireplumber.
And because pipewire-pulse is in recommends of wireplumber that leads
to its installation as well. I am aware of this issue and there was
discussion about that yesterday on #debian-gnome.

Michael Biebl

unread,

Nov 4, 2021, 6:40:03 AM11/4/21

to

Ok, thanks for the clarification. I guess this was an unintentional
change/result?

OpenPGP_signature

Dylan Aïssi

unread,

Nov 4, 2021, 6:40:03 AM11/4/21

to

Le jeu. 4 nov. 2021 à 11:28, Michael Biebl <bi...@debian.org> a écrit :
>
> Ok, thanks for the clarification. I guess this was an unintentional
> change/result?

Unfortunately, yes :-( and I am still unsure how to fix that because
if we remove pipewire-pulse from recommends of wireplumber that will
completely break sound.
I try to reintroduce pipewire-media-session (still in NEW), but it is
a temporary workaround as it it not recommended by upstream devs.

Ralf Jung

unread,

Nov 4, 2021, 11:10:03 AM11/4/21

to

> I don't think this is true at least I don't see any dependency changes in Debian which would automatically install pipewire-pulse.

Well, all I can say is that I did a regular system update and now I have
pipewire-pulse installed. I certainly did not choose to do this myself, so
something did it automatically.

>> Ok, thanks for the clarification. I guess this was an unintentional
>> change/result?
>
> Unfortunately, yes :-( and I am still unsure how to fix that because
> if we remove pipewire-pulse from recommends of wireplumber that will
> completely break sound.
> I try to reintroduce pipewire-media-session (still in NEW), but it is
> a temporary workaround as it it not recommended by upstream devs.

So is the recommendation that users switch back to PulseAudio? What would be the
process for that, i.e., which packages do I have to (un)install?

Kind regards,
Ralf