debcrafters-packages team mailing list archive

[Launchpad Bug Tracker <2109800@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package plymouth - 24.004.60-2ubuntu8

---------------
plymouth (24.004.60-2ubuntu8) questing; urgency=medium

  * d/p/ubuntu-spinner-fsck.patch: listen to /run/systemd/fsck.progress
    (LP: #2109800)

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

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

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

Title:
  systemd-fsckd functionality should be in plymouth directly

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When systemd-fsckd was removed from upstream systemd, a small
  helper/compatibility feature was left behind. When systemd-fsck is
  running, it will connect to /run/systemd/fsck.progress, if it exists,
  and point fsck to that fd for progress updates. The systemd-fsckd patch
  in Ubuntu currently utilizes that, and then sends updates to plymouth.
  This means that we currently have a situation like this:

   systemd-fsck@dev1.service -
   ...                        |-> systemd-fsckd.service -> plymouthd
   systemd-fsck@devN.service -

  In other words, systemd-fsckd.service is a middleware. But, plymouthd
  could simply listen on /run/systemd/fsck.progress itself.

  There is already very similar logic for this in Ubuntu's plymouth via
  debian/patches/ubuntu-spinner-fsck.patch. Instead of carrying the
  large systemd-fsckd patch in systemd, we should consolidate the
  functionality into the existing plymouth patches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2109800/+subscriptions