James provided an alternative that I verified to solve the issue.
jamesh: I know we had trouble with some Rust apps due to pipewire-rs being
incompatible with the old Pipewire[1]. But for some of those cases, the
resulting binaries actually worked with the core22 pipewire since they weren't
using any of the newer features the binding covered. I wonder if Chromium is
similar?
nteodosio: No, it does cause a segmentation fault when attempting a screen
share, <LP#2074358>.
jamesh:
You'll get a
segfault if you mix one version of libpipewire/libspa with a different version
of the plugins.
One test would be to unpack the snap with unsquashfs, remove
all pipewire libraries and plugins, and repack it with snap pack. See if it
still crashes.
[1] https://gitlab.freedesktop.org/pipewire/pipewire-rs/-/issues/75
** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire-rs/-/issues #75
https://gitlab.freedesktop.org/pipewire/pipewire-rs/-/issues/75
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074358
Title:
Screen share causes segmentation fault in Wayland
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2074358/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
