If this is indeed related to the Gentoo bug, I cannot see anywhere in
libseccomp where the environment is being modified. As such I suspect
this is likely actually a bug in systemd where it is modifying the
environment across the exec() and the libseccomp update has just caused
it to actually manifest (due to changed memory layouts as a result of
this new library version / size etc). So assigning this to systemd as
well for now.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886115
Title:
libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1886115/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
