Hello Dan, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.48 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925216 Title: confusing but harmless warning messages printed about syscalls Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] systemd prints messages that complain about system calls such as: /lib/systemd/system/systemd-journald.service:33: Failed to parse system call, ignoring: pidfd_getfd [test case] boot bionic system with 4.15 kernel that does not support pidfd_getfd syscall [regression potential] any regression would prevent correct configuration of seccomp syscall filters, and/or failure to load/parse unit files that contain SystemCallFilter= directives [scope] this is needed only for b this is fixed upstream by commit 13d92c6300edbb1369f97c2e1bef4c4096de8ddb which was included in v238, so this is fixed in focal and later this is not needed for x as seccomp handling is completely different in that older release [other info] as the warning states, the invalid system call is ignored, which is the correct action, and the patch to fix this just changes the log to debug instead of warning (along with consolidation of several flag params into a single flag enum). Thus, no actual change in behavior should occur (other than logging the messages as debug instead of warning). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
