error: unable to write to pipe (Broken pipe)

[YoinkerBoinker]

Describe the bug
When updating the System with pacman -Syu or yay sometimes you'd get "error: unable to write to pipe (Broken pipe)". I can't make sense of it and don't know what's causing it though i saw this popping up in the EndeavourOS Forums a few times and also experienced it on Arch. Running dracut again right after will not bring up the error again. It shouldn't be a space Error since i have 1GB Space for /efi and only one Kernel/Fallback installed. For example my current drive looks like
/dev/nvme1n1p1 999M 101M 898M 11% /efi

Distribution used
have seen this on both Arch and EndeouverOS and on different systems (one is an Intel/NV system the other a Pure AMD System)

Dracut version
059-5

Init system
Systemd

To Reproduce
just update the system using for example yay or pacman -Syu (today is a good day. To do so when using EndeavourOS happend on both my Systems)

Expected behavior
shouldn't happen

Additional context
It'S actually not clear what's the cause of it. It could be visible only since it happens right after creating the Initrd
the Error will look like

"dracut: *** Creating initramfs image file '/efi/XXXXXX/6.7.5-arch1-1/initrd' done ***
error: unable to write to pipe (Broken pipe)"

in case it helps these were the packages that got upgrades

[2024-02-21T15:00:45+0100] [ALPM] upgraded dav1d (1.3.0-1 -> 1.4.0-1)
[2024-02-21T15:00:45+0100] [ALPM] upgraded libffi (3.4.5-1 -> 3.4.6-1)
[2024-02-21T15:00:45+0100] [ALPM] upgraded libvpl (2.10.1-1 -> 2.10.2-1)
[2024-02-21T15:00:45+0100] [ALPM] upgraded giflib (5.2.1-2 -> 5.2.2-1)
[2024-02-21T15:00:45+0100] [ALPM] upgraded highway (1.0.7-1 -> 1.1.0-1)
[2024-02-21T15:00:46+0100] [ALPM] upgraded firefox (122.0.1-1 -> 123.0-1)
[2024-02-21T15:00:46+0100] [ALPM] upgraded firefox-i18n-de (122.0.1-1 -> 123.0-1)
[2024-02-21T15:00:46+0100] [ALPM] upgraded ijs (0.35-5 -> 0.35-6)
[2024-02-21T15:00:46+0100] [ALPM] upgraded jasper (4.2.0-1 -> 4.2.1-1)
[2024-02-21T15:00:46+0100] [ALPM] upgraded lib32-libffi (3.4.5-1 -> 3.4.6-1)
[2024-02-21T15:00:46+0100] [ALPM] upgraded libaio (0.3.113-2 -> 0.3.113-3)
[2024-02-21T15:00:46+0100] [ALPM] upgraded linux-firmware-whence (20240115.9b6d0b08-2 -> 20240220.97b693d2-1)
[2024-02-21T15:00:46+0100] [ALPM] upgraded linux-firmware (20240115.9b6d0b08-2 -> 20240220.97b693d2-1)
[2024-02-21T15:00:46+0100] [ALPM] upgraded openssh (9.6p1-1 -> 9.6p1-3)
[2024-02-21T15:00:46+0100] [ALPM] upgraded qca-qt5 (2.3.8-1 -> 2.3.8-2)
[2024-02-21T15:00:46+0100] [ALPM] upgraded xterm (389-1 -> 390-1)

[davidhaley]

Same.

Version: dracut 059

...
dracut: *** Stripping files done ***
dracut: *** Creating image file '/efi/XXXXXX/6.6.17-1-lts/initrd' ***
dracut: *** Creating initramfs image file '/efi/XXXXXX/6.6.17-1-lts/initrd' done ***
error: unable to write to pipe (Broken pipe)
(13/26) Backing up /boot...
...

[LaszloGombos]

@YoinkerBoinker @davidhaley

Can you please try dracut-git arch package (instead of te dracut arch package) as that is closer to the state of upstream ?

[100busy]

i am also having this same issue. i tried with darcut-git but same result
happening for me with linux-firmware which i saw in @YoinkerBoinker list of packages

[yogo1212]

Hi :-)

Could it be that this has nothing to do with dracut itself but with pacman/libalpm?
I noticed that STDIN is flushed between runs - maybe STDOUT/STDERR are also closed.
I know for certain that this is something that has changed recently in libalpm/pacman because I used to be able to queue multiple yay/pacman invocations by typing them after the prompt and that no longer works.