Comment 12 for bug 2011808
Revision history for this message
| Julian Andres Klode (juliank) wrote | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I have checked that fwupd-signed 1.51.1~20.04.1 successfully boots (with the current shim, not with the previous one, but the shim binaries are the same anyhow as I validated independently in the VM earlier).
By upgrading the same system to focal, removing the boot entry, running fwupdmgr update, removing the capsule files to prevent the update from actually installing (pre-release firmware would break), and then rebooting into working fwupd failing to find the capsule (which is expected).
I previously when started working on this, independently verified the executable can actually install an update on my main machine which has working updates :D