[Bug 1946388] Autopkgtest regression report (systemd/245.4-4ubuntu3.16)

Ubuntu SRU Bot 1946388 at bugs.launchpad.net
Tue Mar 29 14:31:23 UTC 2022


All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.16) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.44.1-1ubuntu1 (arm64, ppc64el, amd64)
linux-aws-5.13/5.13.0-1019.21~20.04.1 (arm64)
snapd/2.54.3+20.04.1ubuntu0.2 (arm64, ppc64el, s390x)
docker.io/20.10.7-0ubuntu5~20.04.2 (s390x)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1946388

Title:
  Journalctl -f --file some.journal causes coredump

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  journalctl -f --file FILE results in segfault

  [test case]

  $ journalctl -f --file $FILENAME

  [regression potential]

  journalctl segfault or failure to properly operate

  [scope]

  needed in focal

  fixed upstream in 2b6df46d21a at v246, so fixed already in h and later

  [original description]

  Focal latest systemd 245.

  Journalctl -f --file path/to/file.journal.  Will allways causes
  journalctl crash...

  The same doesnt happen on centos8 systemd 239... I couldnt test on any
  more systems atm.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1946388/+subscriptions




More information about the foundations-bugs mailing list