Adjusting various tasks for the relevant components. I'm pretty sure this is a regression that is only getting exercised in certain situations of boot entries.
Most notably there was a change was that fwupdate was effectively updated to the "9" release in 0.5-2ubuntu5. This version adds the "Linux Firmware Updater" entry to the boot entry list at the end. If there isn't an "ubuntu" entry earlier on, it's possible that entry is sticking around. The BIOS will only try to build automatic entries if the list was empty, which it's not now. There are two fixes in upstream for this that may help, but that's predicated on my hypothesis being correct. https://github.com/rhboot/fwupdate/commit/9bebde2c8b8960d86326f805743edb9293a6d173 https://github.com/rhboot/fwupdate/commit/cd9ea4cbdc93da922ce9abc45c7de63fe252ecc8 My hypothesis can be confirmed by seeing efibootmgr -v output before a failed update. If currently in a failed state, booting a USB key in UEFI mode (without creating a boot entry in BIOS setup) should be able to indicate this too. ** No longer affects: ubiquity ** Package changed: gnome-software (Ubuntu) => fwupd (Ubuntu) ** Also affects: fwupdate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
