wireplumber sometime segfault on bluez devices disconnect

[Sebastien Bacher]

* Impact

wireplumber sometime segfault on bluez devices disconnect leading to non working pipewire audio

* Test case

Connect and disconnect bluetooth audio devices and ensure wireplumber/pipewire-pulse don't hit an error and sound keeps working in the desktop (sound settings testsound, rhythmbox, firefox playing video)

and check that error reports stop on
https://errors.ubuntu.com/problem/a1b673a5eb264d829f8851e55351dec64a517f53

* Regression potential

The change is in the pipewire bluez plugin so the testing should focus on bluetooth audio devices

[Sebastien Bacher (seb128)]

The corresponding upstream issue is https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/430 and the fix is in the newer version that is going to be synced from Debian

[Timo Aaltonen (tjaalton)]

Hello Sebastien, or anyone else affected,

Accepted pipewire into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pipewire/0.3.65-3ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted pipewire (0.3.65-3ubuntu1) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/44.0-2ubuntu4 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar/update_excuses.html#pipewire

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Andreas Hasenack (ahasenack)]

Hello seb128, this bug has not yet been verified and the package has been in proposed for quite some time, do you think you could perform the verification soon?

[Sebastien Bacher (seb128)]

0.3.65-3ubuntu1 seems to behave stably, the recent reports are from users who didn't upgrade, unsure if it still makes sense to publish lunar updates at this point but still marking as verified

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for pipewire has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package pipewire - 0.3.65-3ubuntu1

---------------
pipewire (0.3.65-3ubuntu1) lunar; urgency=medium

  * debian/patches/git_bluez_disconnect.patch:
    - cherry pick a patch to fix wireplumber segfaulting sometime on
      bluez devices disconnect (lp: #2018316)

 -- Sebastien Bacher <email address hidden> Tue, 02 May 2023 17:56:31 +0200