I am confused - in the initial bug report you mention /etc/systemd/system/dbus-org.freedesktop.resolve1.service as the systemd unit but now you also mention /etc/systemd/system/dbus- org.freedesktop.ModemManager1.service - can you confirm which one you have had to disable the SystemCallFilter?
Also there appear to be a bunch of systemd managed services which have failed to run - could you perhaps downgrade libseccomp back to the previous version and see if this resolves the issue? I think this would be a better solution *for now* than disabling the syscall filter (plus it will help confirm whether this is definitely a causal factor). sudo apt install libseccomp=2.4.1-0ubuntu0.18.04.2 The other option to try and help debug this would be to try and capture a more complete stack trace of the crash - perhaps something like the following might be enough: 1. Ensure the likely offending version of libseccomp is installed (2.4.3-1ubuntu3.18.04.2) (if you downgraded it above) 2. Uncomment out the SystemCallFilter line from the systemd unit 3. Restart the systemd unit (do not reboot) (assuming it is the dbus one you first mentioned): sudo systemctl restart dbus-org.freedesktop.resolve1.service Then with any luck if systemd does crash it at least not be during boot - and apport should catch the crash and create a crash dump. Then you should be able to report this (either as a separate bug or you could attach it to this bug via `apport-bug /var/crash/<crash-dump.crash>` -- 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
