Please consider upstreaming when ready: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62
** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #62 https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62 ** Also affects: plymouth via https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/62 Importance: Unknown Status: Unknown -- 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/2109800 Title: systemd-fsckd functionality should be in plymouth directly Status in Plymouth: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed 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/plymouth/+bug/2109800/+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
