Comment 11 for bug 927097

This bug was fixed in the package bluez - 4.98-2ubuntu1

---------------
bluez (4.98-2ubuntu1) precise; urgency=low

  * Merge with Debian unstable. Remaining Ubuntu changes:
    - Upstart support:
      o Add debian/bluez.bluetooth.upstart.
      o debian/rules: Drop -DEB_UPDATE_RCD_PARAMS
      o Disable 07-fix-639356.patch and don't install 97-bluetooth.rules (in
        debian/bluez.install) and debian/bluez-udev (in debian/rules), we
        don't want to use the udev rules to start bluez. The upstart job does
        that already.
    - debian/bluez-alsa.install: Install ALSA bluetooth configuration into the
      right place for ALSA 1.0.25.
    - Add debian/source_bluez.py Apport package hook. Install in
      debian/bluez.install.
    - debian/control: Build against libnl3-dev, not libnl-dev.
    - debian/socket_audio.patch: re-enable the socket API for the bluetooth
      audio manager. This reverts an upstream change that switches to the
      MediaEndpoint DBus API by default, but it looks like PulseAudio isn't
      quite ready to use that yet. (LP #918736)
    - Add sbc_mmx.patch: Fix building with gcc 4.7. Not applied right now.
    - Drop debian/bluez.preinst and debian/bluez-alsa.preinst: Obsolete
      conffile migrations, 10.04 LTS has a much newer version.
  * 4.98-2 fixes building C++ apps. (LP: #927097)

bluez (4.98-2) unstable; urgency=low

  * Provides proximity.conf by bluez. (Closes: #656889)
    Update debian/bluez.install. proximity.conf was installed to
    etc/bluetooth/proximity.conf.
 -- Martin Pitt <email address hidden> Wed, 22 Feb 2012 10:51:07 +0100