debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #09160
[Bug 2127049] Re: wireplumber crashed with SIGABRT; "assertion failed: (handler != NULL)" in invalid_closure_notify() from closure_invoke_notifiers()
Copying Seb's review here from the linked MR, for visibility,
Thanks for the patch, in fact the package is in sync with Debian and the
fix is included in https://tracker.debian.org/news/1678734/accepted-
wireplumber-0512-1-source-into-unstable/ which was uploaded yesterday.
Since that version will be autosync once resolute archive is open and
syncs started there is no need for a manual upload and a delta, I'm
going to close the merge request
** Changed in: wireplumber (Ubuntu Resolute)
Status: In Progress => Triaged
** Changed in: wireplumber (Ubuntu Questing)
Status: New => Triaged
--
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:
Triaged
Status in wireplumber source package in Questing:
Triaged
Status in wireplumber source package in Resolute:
Triaged
Bug description:
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
References