bluez-alsa devices are invisible to the alsa api and /proc/asound
Bug #1189739 reported by
Forest
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
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.
Revision history for this message
| Konrad Zapałowicz (kzapalowicz) wrote | #1 |
| Changed in bluez (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.