debcrafters-packages team mailing list archive

[Charles <2008149@xxxxxxxxxxxxxxxxxx>]

This is most likely a kernel issue. Did you ever try in Pulseaudio? If
it works there that would be a strong signal there's a pipewire bug, if
not, kernel.

You might also try capturing a bluetooth traffic dump (see:
https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#bluetooth)

Please provide the output of,

 journalctl --user -u pipewire -u pipewire-pulse -u wireplumber -b

After you retrigger the issue.

Also potentially related:
https://bugzilla.kernel.org/show_bug.cgi?id=217539


** Bug watch added: Linux Kernel Bug Tracker #217539
   https://bugzilla.kernel.org/show_bug.cgi?id=217539

** Changed in: pipewire (Ubuntu)
       Status: New => Incomplete

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

-- 
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:
  Incomplete
Status in pipewire package in Ubuntu:
  Incomplete

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