Comment # 19 on bug 1209985 from Andrei Borzenkov

(In reply to Fabian Vogt from comment #17)
> (In reply to Andrei Borzenkov from comment #16)
> > Oh, and what is the actual error in the first place? We may be facing
> > entirely different issue here.
> 
> I made a screenshot of the initial error with verbose shim boot enabled. The
> main messages were:

Attaching this screenshot would be better. Note that BootCurrent is 0019 which
means firmware used "boot from NVMe" entry. In which case it loaded
/boot/efi/EFI/boot/bootx64.efi. While this file itself looks OK, it loads
fallback.efi and it looks old. 

objcopy -O binary -j .sbat /boot/efi/EFI/boot/bootx64.efi
objcopy -O binary -j .sbat /boot/efi/EFI/boot/fallback.efi

Still even if loading fallback.efi fails (it does for me) it should then try to
load MokManager.efi.

objcopy -O binary -j .sbat /boot/efi/EFI/boot/MokManager.efi

Any chance that bootx64.efi and MolManager.efi were updated after the error was
captured?