[pulseaudio-discuss] [PATCH 3/7] alsa, bluetooth: fail if user-requested profile doesn't exist

Tanu Kaskinen tanuk at iki.fi
Thu Oct 29 07:43:46 PDT 2015


On Tue, 2015-10-27 at 08:53 +0100, David Henningsson wrote:
> 
> On 2015-10-27 06:45, Tanu Kaskinen wrote:
> > > Otherwise okay with the behavior change in general - that said, I
> > > haven't checked if we tend to add this somewhere so that this
> > > module
> > > argument is more widely used than we think. Have you?
> > 
> > Sorry, I don't understand what you mean.
> 
> I was just wondering if this module argument is something that is 
> actually used? E g, if we end up using it internally, if some distro 
> sets it by default somehow, etc.

We don't use it internally, and I think pretty much nobody else uses it
either. I believe the modarg broken anyway, because if you load module-
bluez4-device manually without loading module-bluez4-discover, it will
fail to load, because all necessary device data hasn't yet been fetched
from bluetoothd. And it's pretty pointless to load module-bluez4-device 
if you're also loading module-bluez4-discover, because the discovery
module will anyway load all available devices.

-- 
Tanu


More information about the pulseaudio-discuss mailing list