This bug was fixed in the package fwupdate - 0.5-2ubuntu7 --------------- fwupdate (0.5-2ubuntu7) xenial; urgency=medium
* Redo patch series. (LP: #1730343) - Backport ALL patches to EFI application up through the "9" release. - The last two attempts have introduced unobvious bugs due to nature of cherry picking. - The "9" release of the EFI application however has been stable in future releases of Ubuntu. -- Mario Limonciello <mario.limoncie...@dell.com> Mon, 15 Jan 2018 22:59:48 -0600 ** Changed in: fwupdate (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: fwupdate-signed (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu Status in Fwupd: Fix Released Status in fwupd package in Ubuntu: Invalid Status in fwupdate package in Ubuntu: Fix Released Status in fwupdate-signed package in Ubuntu: Fix Released Status in fwupd source package in Xenial: Invalid Status in fwupdate source package in Xenial: Fix Released Status in fwupdate-signed source package in Xenial: Fix Released Status in fwupd source package in Zesty: Invalid Status in fwupdate source package in Zesty: Won't Fix Status in fwupdate-signed source package in Zesty: Won't Fix Status in fwupd source package in Artful: Invalid Status in fwupdate source package in Artful: Fix Released Status in fwupdate-signed source package in Artful: Fix Released Status in fwupd source package in Bionic: Invalid Status in fwupdate source package in Bionic: Fix Released Status in fwupdate-signed source package in Bionic: Fix Released Bug description: [Impact] * A few users have reported instances of not being able to boot into Ubuntu after a firmware update. This is suspected to be caused by a missing Ubuntu boot entry. * fwupdate adds an entry for doing the update to the BootOrder, but doesn't remove it. BIOS auto-creation for making boot entries typically depends on the BootOrder being empty. * This affects all releases of fwupdate since the code to add to BootOrder was also backported into the Ubuntu 16.04 release of fwupdate (0.5-2ubuntu5) [Test Case] * Perform a UEFI BIOS update after installing this package. * Ensure the system boots and there is no longer a "Linux Firmware Updater" entry present in the efibootmgr -v output. [Regression Potential] * Regressions are possible to manifest if any BIOS depends on the previous behavior. * The fixes that were backported have been upstream for a few months and no concerns have been raised upstream from them. [Other Info] Two users have reported that fwupd breaks their Ubuntu installation because the "Ubuntu" EFI boot option disappears after an update. Upstream issue: https://github.com/rhboot/fwupdate/issues/86 To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp