[Bug 1883568] Re: Update focal fwupd to 1.3.11 point release

Mario Limonciello 1883568 at bugs.launchpad.net
Thu Jun 18 16:23:05 UTC 2020


FYI I've adjusted this bug to 1.3.11 because two more high priority issues were identified and fixed and a new point release was spun to include these.  They were related to a TPM PCR0 calculation error and an error encountered updating non-TBT Dell docks.
Given the 1.3.10 was not yet accepted into focal proposed, I feel it's better to include both of those fixes at the same time.

So ~ubuntu-sru or ~ubuntu-archive team member that reviews this, please
reject fwupd 1.3.10 from unapproved queue and instead please take
1.3.11~focal1.

** Summary changed:

- Update focal fwupd to 1.3.10 point release
+ Update focal fwupd to 1.3.11 point release

** Description changed:

- [Impact] 
-  * Upstream has issued a 1.3.10 point release with the following fixes:
-     - Actually reload the DFU device after upgrade has completed
-     - Capture the dock SKU in report metadata
-     - Correctly set the Logitech device protocol
-     - Do not use shim for non-secure boot configurations
-     - Ensure that the DeviceID is set for child devices
-     - Fix an error when detaching MSP430
-     - Fix the DeviceID set by GetDetails
-     - Force the prometheus minor version from 0x02 to 0x01 to fix updates
-     - Parse the CSR firmware as a DFU file
-     - Prevent dell-dock updates to occur via synaptics-mst plugin
-     - Rather than hardcoding thunderbolt to PCI slot numbers, use domain in GUID
-     - Remove a dock device from the whitelist that is never going to be updated
-     - Validate that gpgme_op_verify_result() returned at least one signature
-     - Wait for the cxaudio device to reboot after writing firmware
-  * All but 1 of the patches carried on top of 1.3.9 in Ubuntu focal are also included in 1.3.10 and can be dropped.
+ [Impact]
+  * Upstream has issued a 1.3.11 point release with the following fixes:
+     - Actually reload the DFU device after upgrade has completed
+     - Capture the dock SKU in report metadata
+     - Correctly set the Logitech device protocol
+     - Do not use shim for non-secure boot configurations
+     - Ensure that the DeviceID is set for child devices
+     - Fix an error when detaching MSP430
+     - Fix the DeviceID set by GetDetails
+     - Force the prometheus minor version from 0x02 to 0x01 to fix updates
+     - Parse the CSR firmware as a DFU file
+     - Prevent dell-dock updates to occur via synaptics-mst plugin
+     - Rather than hardcoding thunderbolt to PCI slot numbers, use domain in GUID
+     - Remove a dock device from the whitelist that is never going to be updated
+     - Validate that gpgme_op_verify_result() returned at least one signature
+     - Wait for the cxaudio device to reboot after writing firmware
+     - Add more module types for the Dell dock
+     - Fix the TPM PCR0 calculation
+     - Check for free space after cleaning up ESP
+  * All but 1 of the patches carried on top of 1.3.9 in Ubuntu focal are also included in 1.3.11 and can be dropped.
  
-  * Per the firmware update policy described in
+  * Per the firmware update policy described in
  https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate and
  https://wiki.ubuntu.com/firmware-updates we should jump to point release
  not backport patches
  
  [Test Case]
  
-  * On a device supporting updates, either install a new firmware upgrade
+  * On a device supporting updates, either install a new firmware upgrade
  (fwupdmgr update) or reinstall (fwupdmgr reinstall)
  
-  * verify the update works properly
+  * verify the update works properly
  
  [Regression Potential]
  
-  * Regressions are unlikely as these are all bug fixes that were prompted by users reporting problems.
-  * There are no new features.
-  * If a regression was to pop up it's likely to be very specific to a user's configuration.
+  * Regressions are unlikely as these are all bug fixes that were prompted by users reporting problems.
+  * There are no new features.
+  * If a regression was to pop up it's likely to be very specific to a user's configuration.

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

Title:
  Update focal fwupd to 1.3.11 point release

Status in OEM Priority Project:
  Confirmed
Status in fwupd package in Ubuntu:
  Confirmed
Status in fwupd-signed package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
   * Upstream has issued a 1.3.11 point release with the following fixes:
      - Actually reload the DFU device after upgrade has completed
      - Capture the dock SKU in report metadata
      - Correctly set the Logitech device protocol
      - Do not use shim for non-secure boot configurations
      - Ensure that the DeviceID is set for child devices
      - Fix an error when detaching MSP430
      - Fix the DeviceID set by GetDetails
      - Force the prometheus minor version from 0x02 to 0x01 to fix updates
      - Parse the CSR firmware as a DFU file
      - Prevent dell-dock updates to occur via synaptics-mst plugin
      - Rather than hardcoding thunderbolt to PCI slot numbers, use domain in GUID
      - Remove a dock device from the whitelist that is never going to be updated
      - Validate that gpgme_op_verify_result() returned at least one signature
      - Wait for the cxaudio device to reboot after writing firmware
      - Add more module types for the Dell dock
      - Fix the TPM PCR0 calculation
      - Check for free space after cleaning up ESP
   * All but 1 of the patches carried on top of 1.3.9 in Ubuntu focal are also included in 1.3.11 and can be dropped.

   * Per the firmware update policy described in
  https://wiki.ubuntu.com/StableReleaseUpdates#fwupd_and_fwupdate and
  https://wiki.ubuntu.com/firmware-updates we should jump to point
  release not backport patches

  [Test Case]

   * On a device supporting updates, either install a new firmware
  upgrade (fwupdmgr update) or reinstall (fwupdmgr reinstall)

   * verify the update works properly

  [Regression Potential]

   * Regressions are unlikely as these are all bug fixes that were prompted by users reporting problems.
   * There are no new features.
   * If a regression was to pop up it's likely to be very specific to a user's configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1883568/+subscriptions



More information about the foundations-bugs mailing list