[Bug 1684034] Update Released

[Adam Conrad]

The verification of the Stable Release Update for fwupdate has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1684034

Title:
  Some Dell and Lenovo systems do not work after BIOS Capsule Update

Status in fwupdate package in Ubuntu:
  Fix Released
Status in fwupdate-signed package in Ubuntu:
  Fix Released
Status in fwupdate source package in Xenial:
  Fix Released
Status in fwupdate-signed source package in Xenial:
  Fix Released
Status in fwupdate source package in Yakkety:
  Won't Fix
Status in fwupdate-signed source package in Yakkety:
  Won't Fix
Status in fwupdate source package in Zesty:
  Fix Released
Status in fwupdate-signed source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1.

  The newer version of capsule flashing tools in Ubuntu 17.04 supports
  the reset type from some querycapsuleinfo call：

  https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722

  [Test Case]

  == fwupdate ==
  On a system with a capsule update available, perform capsule update using fwupdate.  Verify the system works properly after the update.

  == efivar ==
  We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies.

  [Regression Potential]
  Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems.  This is actually a BIOS
  problem in those situations.

  It's unlikely that this should happen though because querying for
  reset types more closely aligns to the implementations that other OSes
  use when applying capsule updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+subscriptions