Comment 32 for bug 1864223

Before raising the issue with fwupdmgr, why did not shim load the updater from the entry 0000 as instructed by BootNext? Configuration looks strange, but legit to the eye. Does shim or firmware check for duplicate entries? Does shim or firmware not allow to use entry 0?

Right now, I am unsure what is that "upstream" where I am supposed to bring the discussion. As far as I can see the symptoms, shim is refusing to load fwupdx64.efi for unclear reason. And once again, firmware update _did_ work in eoan!