[Bug 1730343] Re: firmware update breaks Ubuntu

[Mario Limonciello]

I was having some trouble with patching xenial and got busy with something
else, let me try one more time.

On Fri, Dec 1, 2017, 13:40 Mathieu Trudel-Lapierre <mathieu.tl at gmail.com>
wrote:

> There's also a fwupdate-signed waiting in the zesty queue; that should
> fix the current failed-to-upload.
>
> Xenial indeed needs to be updated; perhaps the simplest in this case is
> to bring it to the same version as in zesty?
>
> Mario, what do you think?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fwupdate in Ubuntu.
https://bugs.launchpad.net/bugs/1730343

Title:
  firmware update breaks Ubuntu

Status in Fwupd:
  New
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:
  Triaged
Status in fwupdate-signed source package in Xenial:
  Triaged
Status in fwupd source package in Zesty:
  Invalid
Status in fwupdate source package in Zesty:
  Fix Committed
Status in fwupdate-signed source package in Zesty:
  Fix Committed
Status in fwupd source package in Artful:
  Invalid
Status in fwupdate source package in Artful:
  In Progress
Status in fwupdate-signed source package in Artful:
  Fix Committed
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