Red Hat Bugzilla – Bug 454712
pulseaudio daemon crashes when enabling bluetooth audio device
Last modified: 2008-09-09 15:59:47 EDT
Description of problem:
I was trying to figure out a workaround to BUG454672, where I have a
multi-device pulseaudio setup with not all devices active at the same time... I
was playing around with pacmd, seeing if I could interactively load pulseaudio
With my setup, if I enable a bluetooth audio device at startup (in default.pa or
thereabouts) then the device works correctly.
If I start up pulseaudio without the BT device defined, but then go in with
pacmd and try to load the bluetooth support, it crashes pulseaudio.
With all of the devices defined, here is a snippet from my default.pa:
load-module module-alsa-sink device=intelHDA sink_name=Spkr rate=192000
load-module module-alsa-sink device=plantronicsUSB sink_name=HeadPh rate=44100
load-module module-alsa-sink device=bluetooth sink_name=bluetooth rate=44100
This configuration works (as long as the BT device is powered on, of course --
if the BT is powered off then pulseaudio stalls for a long while and also
sometimes fails to start at all)
If I comment out the last section and feed it line-by-line to a running
pulseaudio daemon using 'pacmd', the daemon crashes on the 'load-module' line.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 311418 [details]
gdb session trace from pulseaudio
I attached a sample gdb session from the pulseaudio failure to see if it would
reveal anything. Note from the trace that 1) many of the stack parameters are
redacted ("value optimized out") and 1) gdb eventually fails with an internal
This seems to be a bug in the BT module for ALSA, not in PA. It is known to be buggy. We now have patches that link PA directly to BlueZ, which will avoid this mess.
I will close this bug now, since it is not a PA bug. Please try the bluezified PA when we have this in rawhide.