I use Pulse-audio and installing the `libspa` package was the final step in getting Blue Tooth to work as-intended on my fresh setup. Installing that package had no other dependencies other than itself that weren't already installed in my Debian system freshly-installed from Live a day earlier.
I can manage the wire-less sound device via Pulse Audio and Blue Man now functions perfectly where before installing that package, it would'n pair. As such, regardless of how or why, I'm going to suggest to you again recommending both packages. You can do a search and see how many people suggest that on-line and others reporting that it too fixed their problems. This would have saved me hours of trouble-shooting and I can also imagine hundreds of other Debian users, especially those less technically-inclined or with less time who'd have just given-up and have no working Bluetooth. Since you are the maintainer, I'll leave it to you to figure out why this fixes the issue. I honestly don't know but I'm here reporting to you that having both packages installed got Blue Man from "doesn't work" to "works flawlessly". Seems like an easy fix with no downsides, especially as `libspa` doesn't depend on a full Pipe Wire installation as far as I can tell. At the very least, there are no explicit conflicts and my system is working well. Thank you again for your time and consideration. Hopefully I've been able to explain the situation more clearly this time around. Cheers! On Sun, 1 Dec 2024 at 05:11, Christopher Schramm <deb...@cschramm.eu> wrote: > Hey, thanks for the suggestion. I might be missing something and there > definitely seems room for improvements, but there is usually no > situation where having both packages makes sense. For Bluetooth audio, > you need Bluetooth support for your system's sound server and that is > typically either PulseAudio or PipeWire, definitely not both. > > With the alternatives in place, if the sound server in use already has > Bluetooth support installed, nothing happens when the recommendations > get checked. If it does not, none of the packages should be installed > already and from my understanding pulseaudio-module-bluetooth will be > chosen simply because it's first in the list. This is unfortunate for > PipeWire users, but pulseaudio still seems more like a default > throughout installations to me, so the opposite does not make sense > either. Recommending both would just mean that users will get Bluetooth > support installed for a sound server that they do not have / use, even > if theirs is already good. At least the pulseaudio module even pulls in > the whole sound server. >
