This bug was fixed in the package systemd - 237-3ubuntu10.42
---------------
systemd (237-3ubuntu10.42) bionic; urgency=medium
[ Dan Streetman ]
*
d/p/lp1860926/0001-networkd-Allow-to-retain-configs-even-if-carrier-is-.patch,
d/p/lp1860926/0002-network-Change-IgnoreCarrierLoss-default-to-value-of.patch,
d/p/lp1860926/0003-network-always-drop-configs-when-corresponding-netwo.patch:
- Add IgnoreCarrierLoss and default to value of ConfigureWithoutCarrier
(LP: #1860926)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9a12a31a62f1a50cd3a67a164ee34c546809815e
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3cc3870fde47982a4dda53f820e18065e5488e7e
* d/e/rules-ubuntu/40-vm-hotadd.rules:
- Hotadd only offline memory and CPUs
(LP: #1876018)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ba305d7ad00e80bc1a03f93e6986eef7cbbb18fc
* d/p/lp1881972-network-strdup-iif-and-oif-when-creating-RoutingPoli.patch:
- Avoid double-free by strdup'ing iif/oif strings for new policy rules
(LP: #1881972)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=874056f0d429aaa2cc872c3b35ec33cd3b740483
* d/p/lp1886197-seccomp-more-comprehensive-protection-against-libsec.patch
- Fix FTBFS on arm64 due to libseccomp changes (LP: #1886197)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c284a72ca2e3d87bfe1c20afb2fcfb379cda544f
*
d/p/lp1832754/0001-umount-Try-unmounting-even-if-remounting-read-only-f.patch,
d/p/lp1832754/0002-umount-Don-t-bother-remounting-api-and-ro-filesystem.patch:
- Try unmounting even if ro-remount fails, and don't bother remounting
api/ro fs
(LP: #1832754)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a518baa673aeaaf42000a3a01b7e03347652b216
[ Alex Murray, Jamie Strandboge ]
* d/p/lp1886115-pid1-fix-free-of-uninitialized-pointer-in-unit_fail_.patch:
- Fix free of uninitialized pointer (LP: #1886115)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=491c76fd0f2fba0007a9b54d63a50f21add643c8
-- Dan Streetman <ddstr...@canonical.com> Wed, 08 Jul 2020 14:59:14
-0400
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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/1886115
Title:
libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
Status in libseccomp package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Fix Released
Status in libseccomp source package in Bionic:
New
Status in systemd source package in Bionic:
Fix Released
Bug description:
[impact]
systemd sometimes crashes on boot due to free of uninitalized var
[test case]
a specific system setup is required, see original description
[regression potential]
any regression would likely involve further crashes on boot.
[scope]
this is needed in b.
this is fixed upstream by commit
58d9d89b4b41189bdcea86c2ad5cf708b7d54aca which is included starting in
v240, so this is included already in f and later.
this is caused by commit 25cd49647c8 which is included starting in
v237, so this bug does not exist in x.
[original description]
After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process. A few seconds into
the boot, the last message displayed is "/var mounted". The system
then appears to hang indefinitely.
Luckily, the 'rescue' boot image allows the boot process to proceed
sufficiently far to allow a root shell to be spawned. Unfortunately no log
files were written during the unsuccessful attempts to boot. Spawning a 2nd
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to
observe the message 'systemd freezing execution' after I closed the first root
shell and resumed the boot process. Further a core file was created (belonging
to /sbin/init) in the root fs
--8<--
(gdb) bt
#0 0x00007f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
#1 0x0000563b957223b7 in ?? ()
#2 <signal handler called>
#3 __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
#4 0x0000563b9577c22e in ?? ()
#5 0x0000563b957672d6 in ?? ()
#6 0x0000563b9576ba22 in ?? ()
#7 0x0000563b9574f51a in ?? ()
#8 0x00007f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
#9 0x00007f16803a53ea in sd_event_dispatch () from
/lib/systemd/libsystemd-shared-237.so
#10 0x00007f16803a5579 in sd_event_run () from
/lib/systemd/libsystemd-shared-237.so
#11 0x0000563b9572a49d in ?? ()
#12 0x0000563b9571560c in ?? ()
#13 0x00007f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3,
argv=0x7ffe78153758,
init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
#14 0x0000563b957164fa in ?? ()
(gdb)
-->8--
and the kernel message buffer lists
--8<--
traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
-->8--
.
To me that looked a bit like Bug 669702 of Gentoo
(https://bugs.gentoo.org/669702) and indeed one of the (few) updates
applied just prior the reboot was the update of libseccomp.
I was able to circumvent the problem by disabling (commenting out) the
syscall filtering requested by systemd (on my system, only
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be
modified).
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-30 (460 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Apple Inc. Macmini5,1
NonfreeKernelModules: wl
Package: systemd 237-3ubuntu10.41 [modified:
lib/systemd/system/systemd-resolved.service]
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
Tags: bionic
Uname: Linux 5.3.0-62-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/24/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM51.88Z.0077.B10.1201241549
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-8ED6AF5B48C039E1
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini5,1
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-8ED6AF5B48C039E1
dmi.modalias:
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
dmi.product.family: Macmini
dmi.product.name: Macmini5,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CurrentDesktop: MATE
Dependencies:
gcc-8-base 8.4.0-1ubuntu1~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.4.0-1ubuntu1~18.04
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-30 (460 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
NonfreeKernelModules: wl
Package: libseccomp2 2.4.3-1ubuntu3.18.04.2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
Tags: bionic
Uname: Linux 5.3.0-62-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1886115/+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
