I understand this is not easy to reproduce, but in case anyone can reliably, please can some share a more detailed log? Increase the log level with
wpctl set-log-level T before you reproduce the crash and then capture attach the log using journalctl --user -u pipewire -u pipewire-pulse -u wireplumber -b Turn off verbose Wireplumber logging with wpctl set-log-level - The output of, pw-dump Will also be useful. I hoped https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/628 would fix this, but it seems not. ** Bug watch added: gitlab.freedesktop.org/pipewire/wireplumber/-/issues #628 https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/628 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2118363 Title: wireplumber crashed with SIGABRT in g_assertion_message_expr() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/2118363/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
