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,
I didn't quite have Dan's patience, but FWIW my system successfully
rebooted 25/25 times with the systemd package (237-3ubuntu10.42) from
bionic-proposed in combination with libseccomp2:amd64
(2.4.3-1ubuntu3.18.04.3) installed and syscall filtering enabled in
with the proposed version of system, i've rebooted 100 times with no
issue, so no obvious regression has been introduced.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you
Hello guenthert, 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.42 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Ok, normally I'd say it's very risky to include a bugfix for a bug that
does not have a clear testcase, especially for a component such as
systemd (high risk). That being said, looking at the actual change -
fixing an uninitialized pointer - I feel much more confident.
--
You received this bug
> I wonder if you see anything related to systemd-resolved with 'journalctl |
> grep audit | grep systemd'
No, not since March 30th.
> at the time of the boot failure.
No log files were written at that time (no log entries made it to disk before
the segfault).
--
You received this bug
** Description changed:
- After applying updates to Ubuntu 18.04 my desktop (apple mini with
+ [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
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This seems related:
* https://bugzilla.redhat.com/show_bug.cgi?id=1653068
* https://github.com/systemd/systemd/pull/11157
I can't say why the libseccomp update would change anything, though the
redhat bug shows an AVC denial, so I wonder if you see anything related
to systemd-resolved with
Note that 2.4.1-0ubuntu0.18.04.2 was previously in bionic and had been
since May of 2019 (2.3.1-2.1ubuntu4 is what bionic was released with,
but later updated to 2.4.1-0ubuntu0.18.04.2). 2.4.1-0ubuntu0.18.04.2 can
be found here:
Thanks - in Ubuntu releases 18.04 onwards debug symbols are provided via
the separate -dbgsyms packages which require extra configuration -
https://wiki.ubuntu.com/DebuggingProgramCrash
TL;DR:
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe
multiverse" | sudo tee
Hmmh, if I see this right, there's a systemd-dbg package available for
Ubuntu 16.04, but not for 18.04.
FWIW, I attached the original core file as bug1886115.core .
** Attachment added: "original core dump of systemd-237-3ubuntu10.41 with
libseccomp2-2.4.3-1ubuntu3"
Ok, since I can't reproduce this locally, if you are interested / able
to help with debugging it, could you please attach the core dump. Or if
this contains potentially sensitive details, you could install the dbg
versions of the packages and reproduce the crash and this would provide
a more
2.3.1-2.1ubuntu4 is the version of libseccomp2 which is available, i.e.
$ sudo apt install libseccomp2=2.3.1-2.1ubuntu4
succeeds. That allowed me to uncomment, i.e. enable, the SystemCallFilter in
/lib/systemd/system/systemd-resolved.service again and reboot successfully.
--
You received this
> can you confirm which one you have had to disable the SystemCallFilter?
Both files are just symlinks to /lib/systemd/system/systemd-resolved.service.
> Also there appear to be a bunch of systemd managed services which have failed
> to run
I moved snap related services out of the way
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?
apport information
** Tags added: apport-collected bionic
** Description changed:
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
> have you customised the syscall filtering in this profile at all?
Don't know what you mean by profile there. The OS runs on bare-metal here.
The only related modification I made has been (now) the reported commenting-out
of
--8<--
SystemCallFilter=~@clock @cpu-emulation @debug @keyring
You can specify the package name using `-p` - so perhaps:
apport-collect -p systemd 1886115
apport-collect -p libseccomp2 1886115
Would do the trick?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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
> apport-collect 1886115
That doesn't seem to succeed (because the installed package is libseccomp2, but
here listed as libseccomp since the former isn't known to launchpad).
I tried
$ apport-bug -u 1886115 libseccomp2
but that appears to attempt to create a new bug, rather then updating the
To capture some more details that might help debug this issue, could you
please run
apport-collect 1886115
in a terminal? This should automatically capture various details and
upload them to this bug report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for reporting this issue. I am not able to reproduce it myself -
have you customised the syscall filtering in this profile at all?
** Changed in: libseccomp (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
23 matches
Mail list logo
