debcrafters-packages team mailing list archive

[Nick Rosbrook <2127049@xxxxxxxxxxxxxxxxxx>]

Are you able to reproduce the issue if you try enough times (within
reason), e.g. by the methods you describe in the impact? If for example
you can reproduce it approximately 1 in 20 attempts, then I would expect
the test plan to at least confirm you can't reproduce it in as many
tries.

I think the existing test plan makes sense as a regression plan, but it
would be good to see a bit more effort to verify the fix is working.

If it's not possible to reproduce in a reasonable number of attempts,
OK. But please note that.

The fix does seem pretty low risk overall, and it's good that upstream
agreed with it.

** Changed in: wireplumber (Ubuntu Questing)
       Status: In Progress => Incomplete

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

Title:
  wireplumber crashed with SIGABRT; "assertion failed: (handler !=
  NULL)" in invalid_closure_notify() from closure_invoke_notifiers()

Status in wireplumber package in Ubuntu:
  Fix Committed
Status in wireplumber source package in Questing:
  Incomplete
Status in wireplumber source package in Resolute:
  Fix Committed

Bug description:
  [ Impact ]

  A significant number of crashes are being reported across releases in
  the Wireplumber shutdown sequence, particularly when switching between
  sessions (gdm-greeter -> user), but also in other situations.

  [ Test plan ]

  Since this is not an easily reproducible issue, the test plan is
  tricky to define. The code changes can be exercised by
  stopping/starting the Wireplumber service. There are no behaviour
  changes related to the permissions store in particular, rather the
  lifecycle.

  [ Where problems could occur ]

  This could cause / expose further race conditions during Wireplumber
  shutdown.

  [ Other info ]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding wireplumber.  This problem was most recently seen with package version 0.5.10-3, the problem page at https://errors.ubuntu.com/problem/a862ecef975d9036153bbb65bf0b0116072763d4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

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