kernel-packages team mailing list archive

[Konrad Zapałowicz <konrad.zapalowicz@xxxxxxxxxxxxx>]

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.

** Changed in: bluez (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, 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

Status in bluez package in Ubuntu:
  Invalid

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1189739/+subscriptions