I get this error message during an automatic upgrade attempt of “Secure Boot dbx” by gnome-software. It is repeatable.
failed to write data to efivarfs: Error writing to file descriptor: Invalid argument
My chrultrabook is a Lenovo IdeaPad Flex 5i Chromebook, it’s a TigerLake, board name LILLIPUP.
I’m not linux-savvy, I just know how to read instructions. I’ve set up my system quite satisfactorily.
Ultramarine is awesome to me, it solved problems I had while running Debian (notably, it wasn’t able to update the kernel automatically).
this is the only problem I’m encountering with it (I didn’t get the problem for the ten months I was running Debian 12). Is it a firmware thing? Is it maybe because it doesn’t recognize the flashed MrChromebox firmware?
But on the Ultramarine Discord, Weird tree Thing explained that “the uefi implementation does not support updates through efi variables”.
So either you ignore this shit as i’ve learned to do (and it’s annoying) or hope that a future mrchromebox release includes updated secureboot info. Which hasn’t happened yet.
I’ve got the same problem (Acer C720 PEPPY, Fedora Workstation 41 / GNOME). Now I just install any other updates that come through, and leave this one sitting there. Annoying, but hey-ho.
MrChromebox releases include the latest secureboot DBX at the time of release. I’m not sure why the update via UEFI NVRAM doesn’t work, and I haven’t had time to diagnose the problem