debcrafters-packages team mailing list archive

[Daniel van Vugt <2008149@xxxxxxxxxxxxxxxxxx>]

Thank you for reporting this bug to Ubuntu.

Ubuntu 22.10 (kinetic) reached end-of-life on July 20, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: bluez (Ubuntu)
       Status: Incomplete => Won't Fix

** Changed in: pipewire (Ubuntu)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2008149

Title:
  Bluetooth Audio Broken After Suspend

Status in bluez package in Ubuntu:
  Won't Fix
Status in pipewire package in Ubuntu:
  Won't Fix

Bug description:
  Release:
  ========
  Description:	Ubuntu 22.10
  Release:	22.10

  Package Version:
  ================
  isa~ apt-cache policy bluez
  bluez:
    Installed: 5.65-0ubuntu1
    Candidate: 5.65-0ubuntu1
    Version table:
   *** 5.65-0ubuntu1 500
          500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
          100 /var/lib/dpkg/status

  Hardware:
  =========
  Model: Apple Inc. MacBookPro9,2

  isa~ lsusb | grep -i blue
  Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller
  Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

  Kmods:
  ======
  bluetooth             827392  54 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm

  Symptom:
  ========
  Pausing sound output (with bluetooth device as sink) will often lead to a failed suspend / resume that leaves audio in an unusable state. Logs indicate that suspend fails, but it looks like the failure path is broken in some way that renders audio unusable when this occurs. This requires a reconnect to recover in all cases, and occasionally even a reboot is required. I have attached debug logs from `bluetooth.service`. I assume hci logs are not required in this case, but if they are please let me know.

  I can test proposed fixes.

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