BlueZ 5.66 release

Bug #1997201 reported by Daniel van Vugt
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Daniel van Vugt

Bug Description

tags: added: upgrade-software-version
Changed in bluez (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Changed in bluez (Ubuntu):
milestone: none → ubuntu-23.04-feature-freeze
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Tarballs are above, and the source code is in:

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I've uploaded this for you.

I did notice that the "original" tarball you provided and is compatible with the Launchpad git tree doesn't match the original tarball used by Debian for 5.66.

Not a problem here, but if we ever did get the bluez packaging closer in sync with Debian, it might be nice to use the same tarballs.

Changed in bluez (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluez - 5.66-0ubuntu1

bluez (5.66-0ubuntu1) lunar; urgency=medium

  * New upstream release 5.66 (LP: #1997201):
    - Fix issue with A2DP and transport connection collisions.
    - Fix issue with allowing application specific error codes.
    - Fix issue with not setting initiator flag correctly.
    - Fix issue with HoG Report MAP size handling.
    - Add initial support for Basic Audio Profile.
    - Add initial support for Volume Control Profile.
  * Refreshed patches:
    - raspi-bcm43xx-load-firmware.patch

 -- Daniel van Vugt <email address hidden> Wed, 30 Nov 2022 16:31:09 +0800

Changed in bluez (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I used the official upstream tarball and just confirmed it matches what we have in the Ubuntu archive. So if Debian is different then that's probably something Debian should fix.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.