debcrafters-packages team mailing list archive

[Launchpad Bug Tracker <1970069@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package systemd - 257.6-1ubuntu1

---------------
systemd (257.6-1ubuntu1) questing; urgency=medium

  * Merge with Debian unstable (LP: #2112075). Remaining changes:
    - debian/tests/boot-and-services: skip apparmor tests on armhf
    - debian/systemd.postinst:
      + manually call systemd-tmpfiles --create in postinst
      + Do not create /etc/tmpfiles.d/tmp.conf on upgrades
    - debian/control:
      + Add Recommends: networkd-dispatcher systemd-resolved to systemd package
      + Make systemd-cryptsetup Priority: important
      + Give systemd-resolved Priority: important
      + Add Recommends: systemd-hwe-hwdb to udev package
      + Drop Recommends: libnss-myhostname libnss-resolve from systemd-resolved
      + Do not build systemd-boot-efi-{amd64,arm64}-signed-template
    - switch-root: use MS_MOVE for /run when switchig from initrd
    - resolve,wait-online: backport wait-online DNS patches
    - test-network: add handling for Ubuntu FAN patches (LP #2104943)
    - d/rules: disable bpf support on riscv64 for now (LP #2099864)
    - d/extra/dbus-1: remove SetLocale restriction from dbus policy (LP #2102028)
    - d/extra/polkit-1: let root ignore inhibitors on reboot etc (LP #2092438)
    - Fix d/extra/initramfs-tools/hooks/udev, so that udev rules that are
      specific to s390x ccw devices are only prevented from being copied if
      zdev_early=0 is set, but copy rules in case of zdev_early=1 or if
      zdev_early is not specified at all. (LP #2102236)
    - Delta for i386:
      + debian/systemd.install: exclude files that are not built for i386
      + debian/systemd.manpages: do not ship un-built manpages on i386
      + debian/rules,debian/control,debian/tests/control:
        Do not build with tpm libraries on i386
      + debian/rules,debian/control,debian/tests/control:
        Do not build with libqrencode on i386
      + debian/rules: Remove unneeded efi artifacts on i386 to avoid debugedit errors
  * Dropped, no longer needed:
    - debian/patches: drop systemd-fsckd patch (LP: #2109800, LP: #1970069)

systemd (257.6-1) unstable; urgency=medium

  [ Luca Boccassi ]
  * d/copyright: use GPL URL instead of old FSF postal address.
  * d/signing-template/copyright: use GPL URL instead of old FSF postal
    address.
  * d/control: bump Standards-Version to 4.7.2, no changes
  * Add version to systemd-boot-efi-signed virtual package. Otherwise
    dependency on systemd-boot-efi-signed (>= 257.5-2) is not satisfiable
    (Closes: #1104663)
  * systemd-homed: add dependency on polkitd (Closes: #1105743)
  * systemd-boot: fix BOOT.CSV usage (Closes: #1106024)
  * Update upstream source from tag 'upstream/257.6' Update to upstream
    version '257.6' with Debian dir
    907f7fd2ae07adbab0ffd7b9235fc25435f12bab
    (Fixes CVE-2025-4598)
  * Drop patches, merged upstream

  [ Tim Small ]
  * document requirement to sync *.link files with initrd (Closes:
    #1005282)

  [ Kirill Rekhov ]
  * Set upstream metadata fields: Security-Contact

systemd (257.5-2) unstable; urgency=medium

  * Backport new patch to workaround /lib64 symlink incompatibility
    (Closes: #1079329)

systemd (257.5-1) unstable; urgency=medium

  * Add NEWS entry to warn about network connectivity loss due to mDNS,
    and workaround
  * Use Conflicts instead of Breaks/Replaces for file move (Closes:
    #1101965)
  * Update upstream source from tag 'upstream/257.5' Update to upstream
    version '257.5' with Debian dir
    2218d137fd911b8d5c2849535b066d27f01406b2
  * Drop backports, included in 257.5
  * Remove conflicts with dracut:arm64 and build nspawn:arm64 again. A
    mutually satisfactory solution for #1079329 has been agreed and is
    being worked on, so temporarily reintroduce #1079329 until it's ready
    in a few days as per agreement with ctte.

systemd (257.4-9) unstable; urgency=medium

  * resolved: break mDNS, remove conflict with avahi. Feedback from users
    is to prefer breaking mDNS rather than avoiding avahi. Ship a drop-in
    to disable mDNS by default, so that users relying on mDNS for
    reachability can hopefully notice it and mask it before upgrading
    (Closes: #1098914)

systemd (257.4-8) unstable; urgency=medium

  [ Luca Boccassi ]
  * systemd.preinst: do not use systemctl libsystemd-shared might not be
    unpacked yet, so check things manually (Closes: #1101698)
  * systemd.preinst: fix shellcheck warnings
  * d/t/boot-and-services: skip gdm3 test in nested LXD run. It is flaky
    and fails half the times, not much value in checking a desktop session
    inside a nested container
  * reintroduce systemd-resolved, with conflict on avahi-daemon. It turns
    out the cloud images have a hard dependency on resolved. In order to
    avoid having to change them, reintroduce the package, with a hard
    conflict on avahi-daemon to avoid reintroducing #1098914 (Closes:
    #1101532)

  [ Yu Watanabe ]
  * d/rules: drop nscd meson option. The meson option was deprecated by
    28f1f1a5e652508d6e61ace8918e8b831e4b62b4 (v257).

systemd (257.4-7) unstable; urgency=medium

  * autopkgtest: when nested tests-in-lxd skips don't fail outer run
  * Backport patches to fix integration tests skipping
  * autopkgtest: re-enable integration tests

systemd (257.4-6) unstable; urgency=medium

  * systemd: conflict with dracut on arm64. Same as the systemd-
    nspawn/arm64 changes of 257.4-4. As correctly pointed out on the
    reopened #1079329 this combination also creates incompatibilities, so
    add an explicit package conflict to fix this occurrence too as
    requested by the reporter. (Closes: #1079329)
  * d/control: fix systemd-boot and systemd-boot-tools descriptions
  * Add Lintian override for 'unknown-field Protected'

systemd (257.4-5) unstable; urgency=medium

  * Add missing dh-exec shbang to d/systemd-tests.install

systemd (257.4-4) unstable; urgency=medium

  [ Luca Boccassi ]
  * Update tzdata-legacy version constraint for new bookworm-p-u tzdata
    version
  * systemd-boot: do case-insensitive parsing of efibootmgr output
    (Closes: #1100653)
  * userdbd: use wildcard to install units
  * systemd-container: use more wildcards to install files
  * Handle new tmp mount on upgrade in preinst rather than postinst. Avoid
    race with new units being activated and pulling it in at the same time
    (Closes: #1101175)
  * autopkgtest: remove workaround for 'meson compiile mkosi' and use
    'mkosi -f' instead to avoid slow rebuilds
  * autopkgtest: drop versioning constraints on tzdata. These do not seem
    to be necessary in order for autopkgtest to pull in the package, so
    drop them as they need to be constantly updated due to p-u uploads
  * Move leftover resolved files to its own package. A few files were
    mistakenly shipping in the main systemd package even though they are
    part of resolved, due to a refactor from some time ago. Move them
    over.
  * Drop systemd-resolved package. The ctte has declared that the way the
    systemd-resolved tool works is incompatible with their decision to
    prioritize avahi in Debian. Furthermore, the resolved tool is being
    used to inflict pain on the maintainer, and induce burnout.
    Regrettably, the only safe solution to ensure this package is
    compliant with this decision is to drop it, as all reasonable
    alternatives put forward have been rejected:
    https://salsa.debian.org/systemd-team/systemd/-/merge_requests/289
    (Closes: #1098914)
  * Drop systemd-nspawn on arm64. The ctte has declared that the way the
    systemd-nspawn binary works on arm64 is incompatible with their
    decision to leave in place a recently introduced change in the debian-
    specific base-files package, which caused a dpkg regression.
    Furthermore, the nspawn tool is being used to inflict pain on the
    maintainer, and induce burnout. Regrettably, the only safe solution to
    ensure this package is compliant with this decision is to drop the
    binary on arm64, as all reasonable alternatives put forward have been
    rejected:
    https://salsa.debian.org/systemd-team/systemd/-/merge_requests/289
    (Closes: #1079329)

  [ Nick Rosbrook ]
  * Add myself to Uploaders

  [ Andrea Pappacoda ]
  * d/control: only conflict against opensysusers << 0.7.3-4.1~
    opensysusers 0.7.3-4.1 is no longer co-installable with systemd as it
    conflicts with systemd-sysusers, so it is no longer needed to conflict
    against it systemd-side.

systemd (257.4-3) unstable; urgency=medium

  * Fix versioned breaks/replaces for sd-boot-tools (Closes: #1100412)

systemd (257.4-2) unstable; urgency=medium

  * Split bootctl to new systemd-boot-tools package (Closes: #1086860)

 -- Nick Rosbrook <enr0n@xxxxxxxxxx>  Fri, 30 May 2025 10:56:19 -0400

** Changed in: systemd (Ubuntu)
       Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2025-4598

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+subscriptions