are you sure the problem is with pulseaudio?
I don't know that the problem lies totally with pulseaudio.
However, the need to do a pactl load-module module-bluetooth-discover
even though the module is already specified to be loaded in
, suggests at least part of the problem
lies with PA. Beyond that, I don't know the underlying mechanisms
well enough to diagnose it well (I never even heard of PulseAudio
until I started researching this problem!).
I just reinstalled Mint 17.2, because I decided to convert my disk
from traditional partitions to LVM. I only now have gotten back to
examining the audio issue. What I am seeing now seems to be
slightly different behavior than what I observed before, though
I am not 100% certain of that.
What I find now:
- I can pair with the headset just fine.
- The volume control (pavucontrol) does not know about the device.
- Issue the aforementioned pactl load-module command. Volume control still does not notice the device.
- Reconnect the bluetooth device. pavucontrol now becomes
aware of the device. I suspect that if I had done the load-module
before pairing the headset, it would have been noticed the first time
around (I am guessing that there is some sort of interprocess notification
mechanism that is not happening unless the module is loaded, and that
loading the module does not retroactively broadcast notifications about already connected devices).
- Though pavucontrol is aware of the device -- it shows up under
the Configuration tab -- it still is not shown under the
Output Devices tab.
- To fix the above problem, I must go to the Configuration
pane and explicitly turn off all other devices. Then enable the headset.
pavucontrol does let me select high fidelity (A2DP) mode for
the headset at this time. Now the audio comes through the headset, and in
- If I re-enable other devices under the config tab, pavucontrol
will show all of them in the Output Devices pane. However it is not
possible to select which one is active, much less do something more
sophisticated such as enabling simultaneous output on multiple devices.
It just seems to choose one device more or less at random, and it cannot be
changed without manually disabling all other devices than the desired one.
What really bothered me is that bluetooth work flawlessly
in Mint 13 Mate
Agreed. It worked flawlessly for me too in the past (I was using
Ubuntu 10.04 then). The sound icon in the notification area of the
desktop also allowed for instant and easy selection of any available
output device without needing to start up another application like
. This is a serious regression.
I run a script in startups to make pulseaudio do the right
thing on boot...
Yah, I thought of doing the same. I'm curious about the "sleep 20"
you put in your script. Why was that needed?