that's the gist of my comment on the tracking issue... not sure if Timothee would have feedback but i bet he's slammed with all this on top of normal stuff so i don't want to bug him about it
i'd like to better understand how having bootupd installed would have "magically" saved us... it's not clear to me yet since i'm not aware of us directly requesting it to do anything
"Fedora Atomic systems (rpm-ostree based systems) do not update the BIOS / EFI bootloaders files by default on updates as this operation may fail and leave the system in an un-bootable state. The bootupd project has been created to fix this issue, creating a user/administrator triggered process to update the bootloader."
on bazzite there's a different issue from stock atomic or even ublue, given the fully custom signed kernel, i don't think bazzite really relies on the shim given they don't use the fedora signed kernel
so like, if we know we can get all the hw info + rpm-ostree status + whatever else we may think is useful then users would only ever have to worry about the one command
plus the nice thing is people can start socializing it now, so as we figure out new things to ask for it can be totally flexible in that way, but the command will remain the same for the users, which will pay off dividends over time
systemctl reboot --firmware-setup doesn't support this. That command calls: org.freedesktop.login1.Manager SetRebootToFirmwareSetup, which is the DBUS interface of systemd-logind.
@M2 do you have some free time sometime today to review your PR? I'm trying to reconcile how I can get it added to the testing branch to actually test your code.