I haven't been able to reproduce this issue still, and further analysis
hasn't provided a completely clear idea of the right fix to justify
another trip through the SRU process. I've documented what ideas I've
found so far and asked upstream for help.
** Changed in: wireplumber (Ubuntu Questing)
Status: In Progress => Triaged
** Changed in: wireplumber (Ubuntu Resolute)
Status: In Progress => Triaged
** Bug watch added: gitlab.freedesktop.org/pipewire/wireplumber/-/issues #881
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/881
** Also affects: wireplumber via
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/881
Importance: Unknown
Status: Unknown
--
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/wireplumber/+bug/2127049/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
