I'm having the same problem, but even the workaround did not work for me
in every application. Notably flashplugin-nonfree (with libflashsupport)
and gnome-sound-properties PulseAudio test beep (!) still use the wrong
sound card. To my knowledge, they use PulseAudio natively.
$ cat ~/.pulse/default-sink
alsa_output.pci_1412_1724_sound_card_0_alsa_playback_0
$ cat /etc/pulse/default.pa | grep default-sink
set-default-sink alsa_output.pci_1412_1724_sound_card_0_alsa_playback_0
Both are correct. I think the problem is:
$ pulseaudio -C
>>> list-sinks
index: 0
name: <alsa_output.pci_10de_371_sound_card_0_alsa_playback_0>
....
index: 1
name: <alsa_output.pci_1412_1724_sound_card_0_alsa_playback_0>
....
It seems that PulseAudio has the same age-old problem like ALSA.
Applications just use index 0 while they should be fetching the default
device. I consider this a bug in PulseAudio because it lets this happen;
set-default-sink should either force the device to index 0, or for the
very least there should be big warning signs in the documentation for
developers.
I've been able to set indices manually in ALSA by editing
/etc/modprobe.d/alsa-base, but I haven't found similiar solution to
PulseAudio. My workaround for the moment is killall pulseaudio.
--
The user cannot select sound card
https://bugs.launchpad.net/bugs/229137
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
