I just ran into https://github.com/fwupd/firmware-lenovo/issues/53 (updating firmware fails, saying something like "fwupd failed to write data to efivarfs: no space left"). The solution mentioned in the comments there (back up /sys/firmware/efi/efivars/, rm /sys/firmware/efi/efivars/dump-type0*, reboot) works fine, but I wonder if firmware-manager can take care of this behind-the-scenes, possibly by some combination of selectively deleting dumps and/or disabling their creation in the first place (as discussed in the comments on that issue).
Anyway, just wanted to flag this. It seems like the issue could be distro-dependent and that this repo is the appropriate place to discuss it for pop.
I just ran into https://github.com/fwupd/firmware-lenovo/issues/53 (updating firmware fails, saying something like "fwupd failed to write data to efivarfs: no space left"). The solution mentioned in the comments there (back up
/sys/firmware/efi/efivars/
,rm /sys/firmware/efi/efivars/dump-type0*
, reboot) works fine, but I wonder if firmware-manager can take care of this behind-the-scenes, possibly by some combination of selectively deleting dumps and/or disabling their creation in the first place (as discussed in the comments on that issue).Anyway, just wanted to flag this. It seems like the issue could be distro-dependent and that this repo is the appropriate place to discuss it for pop.