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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127049
Title:
wireplumber crashed with SIGABRT; "assertion failed: (handler !=
NULL)" in invalid_closure_notify() from closure_invoke_notifiers()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2127049/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
