[Bug 1730343] Re: firmware update breaks Ubuntu
Ćukasz Zemczak
1730343 at bugs.launchpad.net
Thu Jan 18 08:24:53 UTC 2018
Hello Merlijn, or anyone else affected,
Accepted fwupdate into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/fwupdate/0.5-2ubuntu7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: fwupdate (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags removed: verification-failed-xenial
** Tags added: verification-needed-xenial
** Changed in: fwupdate-signed (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
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:
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 Committed
Status in fwupdate-signed source package in Xenial:
Fix Committed
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
More information about the foundations-bugs
mailing list