← Back to team overview

kernel-packages team mailing list archive

[Bug 1169776] Re: Bluetooth audio fails on 64-bit architecture


This bug is being reproduced in Xubuntu too and we are currently in

Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.1 LTS
Release:	14.04
Codename:	trusty
Arch: x86_64

Today I've received an update for bluez and pulseaudio but it seems to
keep failing. I'm using a Plantronic ML18 headset recognized as
PLT_ML20. When I pair the device and make the audio sink the device is
not listed in pulseaudio device list.

I think is a bug from Blueman.
Could you check this issue? Is very frustrating to swap to another SO just for use several communications tools.

Thank you

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.

  Bluetooth audio fails on 64-bit architecture

Status in bluez package in Ubuntu:

Bug description:
  * Headset works fine on 32-bit machines under Ubuntu 12.04, 12.10
       (Samsung NC-20, Dell D420)

  * Same headset pairs, but fails to do audio on a 64-bit machine, Ubuntu 32-bit or 64-bit 12.10 or 64-bit 13.04
      (Lenovo S206 with AMD E1-1200)

  AGAIN: it fails on 64-bit *machines* regardless of the Ubuntu version,
  and works on 32-bit machines.

  * At first sometimes I see the hardware in the Sound Settings.
    but only hear some tinny, scratchy sounds briefly.
    Then the device disappears from the Sound Settings.  Re-starting bluetooth has no effect.

  On a working system, see syslog lines like
      bluetoothd[825]: /org/bluez/825/hci0/dev_<bluetooth-id>: fd(32) ready
      bluetoothd[825]: Audio connection got disconnected

  But on the non-working systems, I don't see such bluetooth lines at all (I presume due to the logging level)
  Anyway, no *errors* are showing, after pairing with the headset.  The audio just doesn't work.

  Please advise how to debug.

  (Of course I don't know if the blame lies with the Bluetooth software
  or with PulseAudio, and of course I don't care.)

  Please fix this soon!  I have been using this on a daily basis, and
  need to move to a newer machine.

To manage notifications about this bug go to: