[Bug 1189739] [NEW] bluez-alsa devices are invisible to the alsa api and /proc/asound
Forest
1189739 at bugs.launchpad.net
Tue Jun 11 06:36:59 UTC 2013
Public bug reported:
Bluetooth devices do not show up in the sound device lists presented by
ALSA applications, even when bluez-alsa is installed and working. This
means that, unless a program happens to allow manually-specified ALSA
device name strings and the user knows what magic string to enter and
how to do so, bluez-alsa is effectively useless.
I have verified that this is not simply an application bug by writing my
own libasound test application: All the other sound devices in my system
are enumerated by ALSA API calls, but my bluetooth headset is notably
absent. There is no entry for it in /proc/asound either, so it seems
there is simply no way to discover a bluez-alsa device. What a shame.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1189739
Title:
bluez-alsa devices are invisible to the alsa api and /proc/asound
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1189739/+subscriptions
More information about the Ubuntu-bluetooth
mailing list