Upgrade fwupd for Atomic Docking Support

[Yuan-Chen Cheng]

This is to support Dell's new Atomic Docking and WD22TB4 in focal.

As fwupd 1.7.x efi split is done, let use 1.7.5 for this.

In this SRU, it include source package: fwupd-efi, fwupd, fwupd-signed and
libjcat (LP: #1961864)

[Impact]

 * Several components that are used in OEM projects need
   to use the fwupd to support firmware update.

 * This will follow the SRU exception in
   https://wiki.ubuntu.com/firmware-updates

[Test Plan]

 * follow the steps in the SRU exception page.
   Need to make sure it still works well even if secure
   boot is on.

 * Given fwupd 1.7.4 is so new, I think we should extended
   the date in proposed channel like 14 days.

 * Plan to loop existing OEM project and also request for
   more regression tests.

[Where problems could occur]

 * BIOS upgrade failed and brick the machine:
   We test the fwupd in PPA and this does not happen. Given past
   experience, this only happens as we use unstable/not-tested
   bios from vendors.

 * component fw upgrade and the component no longer working:
   Per OEM team experience, this only happens as we use
   unstable/not-tested fw from vendors, or there are special
   steps and we didn't follow up carefully enough.

 * component fw upgraded and kernel driver/firmware in the ubuntu
   the archive does not support it:
   This is possible but has rarely happened before. And this is so
   hard to know in advance if IHV didn't do their job well.
   This only happened in case that the failed fw is not supported
   in the previous fwupd, but it supported in the new fwupd, and
   the new fw happened not been supported by existing
   kernel driver/linux-firmware deb.
   We will notify OEM projects to be aware of it, so it won't
   break things.

 * Other possible failures: those are well-covered in the SRU
   exception test plan.
   - fwupd does not work as Secure boot is on.
   - dbus interface in-compatibility.

[Other Info]

 * Two bugs will also be fixed with this SRU: lp:1954965, lp:1953573.

[Mario Limonciello (superm1)]

FYI all the packaging doing the split for 1.7.x is ready for debian, but it's pending sponsorship and alignment with ftp-master.

[Mario Limonciello (superm1)]

Specifically staged here:
fwupd-efi: https://salsa.debian.org/efi-team/fwupd-efi/-/tree/debian/unstable
fwupd: https://salsa.debian.org/efi-team/fwupd

The packaging should be ready for both Debian and Ubuntu, but has been intentionally waiting to upload to Ubuntu until it can be sponsored into Debian and ack-ed by ftp-master in case anything needed to be changed that would make syncing more challenging. They can technically be reviewed to go to Ubuntu now as well if desirable.

[Yuan-Chen Cheng (ycheng-twn)]

Just found that they don't really need SRU fwupd to support new docking very soon.

IMHO, If Debian didn't land 1.7.x in unstable before a certain day, then Ubuntu should just go land it so it's available in 22.04.

[Sebastien Bacher (seb128)]

@Yuan, right, I'm going to wait until december and upload to Ubuntu if there is no update

[Yuan-Chen Cheng (ycheng-twn)]

for the record, for today:

1. debian sid: 1.5.7
2. upstream: 1.7.2

[Sebastien Bacher (seb128)]

The new fwupd and fwupd-efi have been uploaded to jammy now

[Yuan-Chen Cheng (ycheng-twn)]

per request by the customer, we'd like to support the atomic docking in focal by using fwupd 1.5.13

AI: wait 1.7.x land in jammy.

plus

Plan 1:
- land 1.5.13 in impish.
- SRU 1.5.13 in focal.

OR
Plan 2:
- SRU 1.7.X in impish.
- SRU 1.7.X in focal.

If we want to use the same fwupd-efi binary across all releases, we need to go plan 2.

[Yuan-Chen Cheng (ycheng-twn)]

some said other OEM project need 1.7.x on focal. Wait a bit for details to come.

[Yuan-Chen Cheng (ycheng-twn)]

we need 1.6 in focal per lp:1954965.

I don't think we'd like such version diversity. Let's also SRU 1.7.x back to focal.

[Mario Limonciello (superm1)]

Fixed in Jammy by the 1.7.1 upgrade.

[Yuan-Chen Cheng (ycheng-twn)]

first ppa for focal and impish.

https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd-17x-v2

Note:

1. No plan to prepare deb for hirsute
2. if you want to test secure boot, install fwupd-signed from jammy.
   I kind of believe we will copy the fwupd-signed binary from jammy
   to focal and impish.

[Yuan-Chen Cheng (ycheng-twn)]

fwupd-signed from the jammy-update archive.

[Mario Limonciello (superm1)]

#11:
I think you'll want to update it to 1.7.4 which is in Jammy now so to keep them the same at least for now.

[Yuan-Chen Cheng (ycheng-twn)]

Will put that on my queue, thank you for your notice.

[Yuan-Chen Cheng (ycheng-twn)]

fwupd 1.7.4 ppa:

https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd174

[Yuan-Chen Cheng (ycheng-twn)]

note that the deb in the #15 ppa got positive test results with atomic docking and wd22tb.

[Yuan-Chen Cheng (ycheng-twn)]

Note on SRU:

1. shall we also SRU libjcat from jammy to focal/impish?
   fwupd is the only consumer of libjcat. For now, there is no
   major bug needed also to SRU libjcat, however, it seems
   better also to SRU it so that we have consistent behaviors.
2. Per what I know, we'd like to use the same efi binary cross
   series. Given so, maybe a binary copy of fwupd-efi related
   binary shall work.

[Yuan-Chen Cheng (ycheng-twn)]

fwupd dbus 1.7.3 interface change compare to 1.5.11. It looks fine per
previously test criteria we define in the SRU exception.

$ diff -u fwupd-dbus-1.5.11.log fwupd-dbus-1.7.3.log
--- fwupd-dbus-1.5.11.log 2022-01-28 13:02:17.288157828 +0800
+++ fwupd-dbus-1.7.3.log 2022-01-28 13:02:02.476101470 +0800
@@ -1,4 +1,4 @@
-method return time=1627442048.298940 sender=:1.120 -> destination=:1.122 serial=264 reply_serial=2
+method return time=1643346039.053383 sender=:1.114 -> destination=:1.190 serial=1220 reply_serial=2
    string "<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
                       "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
 <!-- GDBus 2.64.6 -->
@@ -76,10 +76,20 @@
       <arg type="aa{sv}" name="attrs" direction="out">
       </arg>
     </method>
+ <method name="GetHostSecurityEvents">
+ <arg type="u" name="limit" direction="in">
+ </arg>
+ <arg type="aa{sv}" name="attrs" direction="out">
+ </arg>
+ </method>
     <method name="GetReportMetadata">
       <arg type="a{ss}" name="attrs" direction="out">
       </arg>
     </method>
+ <method name="SetHints">
+ <arg type="a{ss}" name="hints" direction="in">
+ </arg>
+ </method>
     <method name="Install">
       <arg type="s" name="id" direction="in">
       </arg>
@@ -190,8 +200,14 @@
       <arg type="a{sv}" name="device">
       </arg>
     </signal>
+ <signal name="DeviceRequest">
+ <arg type="a{sv}" name="request">
+ </arg>
+ </signal>
     <property type="s" name="DaemonVersion" access="read">
     </property>
+ <property type="s" name="HostBkc" access="read">
+ </property>
     <property type="s" name="HostProduct" access="read">
     </property>
     <property type="s" name="HostMachineId" access="read">

[Sebastien Bacher (seb128)]

I've uploaded the packages in the SRU queue for impish now

Let's start with that serie to check how the SRU team feels about the updates and get some testing before uploading for the LTS.

Wontfixing for hirsute as it's not likely we will SRU to that serie now

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd-efi into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd-efi/1:1.2-2~21.10.1 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, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd-efi into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd-efi/1:1.2-2~20.04.1 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd/1.7.3-1~21.10.1 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, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd/1.7.4-1~21.10.1 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, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd/1.7.4-1~20.04.1 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd-signed into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd-signed/1.42~ubuntu21.10.1 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, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd-signed into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd-signed/1.27.1ubuntu6 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Steve Langasek (vorlon)]

The SRU of fwupd adds a new Recommends on fwupd-unsigned which is incorrect. The incorrect added package relationship was detected because the package in focal-proposed is in universe and this causes an image build failure; but while fwupd-unsigned should be promoted to main as it is in jammy, it is still wrong to pull it in at runtime as a Recommends. I am therefore rejecting this fwupd SRU which will require a reupload.

Future uploads should include an explicit SRU process around any changes to the packaging (as opposed to the upstream exception) that are being SRUed.

[Mario Limonciello (superm1)]

That's a side effect of the fwupd/fwupd-efi split.

It truly is optional in the version that YC is doing the SRU. The daemon will check for the EFI binary existing at the time of installing a firmware update (either signed or unsigned depending upon circumstances) and will issue an error message to the calling client if it's missing.

This means that an end user with a machine that will never take EFI updates can remove the package if they want.

[Yuan-Chen Cheng (ycheng-twn)]

Guess Steve means we need to explicitly tell the SRU team that they need to copy fwupd-unsiged into main in the first place we do SRU.

It is just something that nobody has the whole picture and things just happen at the same time maybe.

[Mario Limonciello (superm1)]

I notice Steve just uploaded to Jammy a change that removes the Recommends.

I don't really understand why; IMO it really should be a Recommends.
- If you have secure boot disabled you use the binary provided by fwupd-unsigned.
- If you have secure boot enabled you use the binary provided by fwupd-signed.

[Yuan-Chen Cheng (ycheng-twn)]

IMO, use the signed one as the secure boot disable seems harmless.

However, that makes it a little annoying in the development phase (ex: share build in PPA) if we have fwupd / fwupd-efi version dependency in the future.

[Mario Limonciello (superm1)]

In theory it sounds harmless, but in practice there was a long period of time that shim chainloading to fwupd was broken in Ubuntu.

If we didn't have that codepath available to use the non-signed EFI package without chainloading through shim there wouldn't have been a workaround to install firmware updates during this breakage.

[Yuan-Chen Cheng (ycheng-twn)]

@Mario, the annoying means: we still can ask the one who run the testing to manually install fwupd-unsigned and turned off secure boot to do the testing. This is still working if we need to use the non-signed EFI, right?

[Mario Limonciello (superm1)]

Yeah that still works, and is exactly why it should remain a Recommends. You should be able to have SB off, apt install fwupd and have it work for UEFI updates.

[Yuan-Chen Cheng (ycheng-twn)]

per test, if fwupd-unsigned is not installed, then re-install bios will be failed if secure boot is not turned on.

We need a patch around https://github.com/fwupd/fwupd/blob/main/plugins/uefi-capsule/fu-uefi-common.c#L89

[Yuan-Chen Cheng (ycheng-twn)]

Steve and Mario, I create another bug for not install fwupd-unsigned in lp:1960783

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd/1.7.5-3~21.10.1 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, what testing has been performed on the package and change the tag from verification-needed-impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-impish. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Łukasz Zemczak (sil2100)]

Hello Yuan-Chen, or anyone else affected,

Accepted fwupd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/fwupd/1.7.5-3~20.04.1 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, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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 for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Yuan-Chen Cheng (ycheng-twn)]

for focal and impish, they both upgrade fwupd from 1.5.11 to 1.7.5

fwupd dbus 1.7.5 interface change compare to the existing 1.5.11. It looks fine per
previously test criteria we define in the SRU exception.

$ diff -u fwupd-dbus-1.5.11.log fwupd-dbus-1.7.5.log
--- fwupd-dbus-1.5.11.log 2022-03-02 06:31:45.690734046 +0800
+++ fwupd-dbus-1.7.5.log 2022-03-02 06:32:02.683328536 +0800
@@ -1,4 +1,4 @@
-method return time=1627442048.298940 sender=:1.120 -> destination=:1.122 serial=264 reply_serial=2
+method return time=1646173922.685521 sender=:1.87 -> destination=:1.93 serial=613 reply_serial=2
    string "<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
                       "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
 <!-- GDBus 2.64.6 -->
@@ -76,10 +76,20 @@
       <arg type="aa{sv}" name="attrs" direction="out">
       </arg>
     </method>
+ <method name="GetHostSecurityEvents">
+ <arg type="u" name="limit" direction="in">
+ </arg>
+ <arg type="aa{sv}" name="attrs" direction="out">
+ </arg>
+ </method>
     <method name="GetReportMetadata">
       <arg type="a{ss}" name="attrs" direction="out">
       </arg>
     </method>
+ <method name="SetHints">
+ <arg type="a{ss}" name="hints" direction="in">
+ </arg>
+ </method>
     <method name="Install">
       <arg type="s" name="id" direction="in">
       </arg>
@@ -176,6 +186,8 @@
       <arg type="s" name="sig" direction="out">
       </arg>
     </method>
+ <method name="Quit">
+ </method>
     <signal name="Changed">
     </signal>
     <signal name="DeviceAdded">
@@ -190,8 +202,14 @@
       <arg type="a{sv}" name="device">
       </arg>
     </signal>
+ <signal name="DeviceRequest">
+ <arg type="a{sv}" name="request">
+ </arg>
+ </signal>
     <property type="s" name="DaemonVersion" access="read">
     </property>
+ <property type="s" name="HostBkc" access="read">
+ </property>
     <property type="s" name="HostProduct" access="read">
     </property>
     <property type="s" name="HostMachineId" access="read">

[Yuan-Chen Cheng (ycheng-twn)]

on focal, target machine: Latitude 5300, with the fwupd/fwupd-signed in the proposed channel, secure boot on, reinstall system bios, test passed.

[Yuan-Chen Cheng (ycheng-twn)]

on focal, with the fwupd/fwupd-signed in the proposed channel, test passed on the following items:

1. upgrade OS bios from snap-store: passed
2. upgrade WD19 FW from gnome-software: passed
3. reinstall firmware of WD19, a NVME module: passed

[Yuan-Chen Cheng (ycheng-twn)]

dirk test install local cab for wd22tb4 and atomic docking with fwupd from the focal-proposed channel, and it test passed.

I also run the fwupd-tests old/new version and both passed.

[Yuan-Chen Cheng (ycheng-twn)]

test on jammy, install fwupd/libjcat1 from focal proposed channel.
secure boot on

1. upgrade install nvme fw from snap-store: passed
2. upgrade os bios cab from the command line: passed
3. upgrade os bios from gnome-software: passed
4. upgrade WD19SC fw from gnome-software: passed

Above items is tested on Precision 7730.

5. AI: upgrade Atomic docking fw.

[Kai-Chuan Hsieh (kchsieh)]

test on impish, install fwupd/libjcat1 from focal proposed channel.

fwupd: 1.7.5-3~21.10.1
libjcat1: 0.1.4~0ubuntu0.21.10.1

enable dell test remote channel
$ sudo fwupdmgr update

upgrade Atomic docking fw: passed

Devices that have been updated successfully:

 • VMM6210 in Dell dock (06.04.03 → 06.04.05)
 • Package level of Dell dock (01.00.00.00 → 01.00.02.01)
 • HD22Q (00.00.00.09 → 01.00.00.01)

[Łukasz Zemczak (sil2100)]

One worrying thing we discussed today with YuanChen Cheng about the fwupd situation is the fact of an unversioned dependency on libjcat1 right now. I am a bit concerned that there is no versioned dep in neither of the packages, meaning that some users might only upgrade fwupd but not libjcat1 and therefore not be able to get the latest firmware upgrades. So they'd have to upgrade fully to get this experience.

This, however, is seemingly also the case in jammy and even in Debian with 1.7.6-1. I think with the nearest follow up upload we need to make sure that users upgrading to latest fwupd also get the latest dependencies. From what YuanChen told me, it seems to not cause any breakages, simply inability to get the latest firmware (older ones are fine). Even though this is not a perfect situation, I guess we can live with it for a short moment.

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwupd - 1.7.5-3~21.10.1

---------------
fwupd (1.7.5-3~21.10.1) impish; urgency=medium

  * Backport 1.7.5-3 from jammy to impish.
  * Support several new devices (LP: #1949412, LP: #1954965, LP: #1953573)
  * fwupd / fwupd-efi source package split (LP: #1955386)
  * Don't install new fwupd-unsiged by default. (LP: #1960783)

 -- Yuan-Chen Cheng <email address hidden> Mon, 21 Feb 2022 00:12:49 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwupd-efi - 1:1.2-2~21.10.1

---------------
fwupd-efi (1:1.2-2~21.10.1) impish; urgency=medium

  [ Yuan-Chen Cheng ]
  * Upload as par of the new fwupd 1.7 serie SRU, needed for hardware
    as the Dell's new Atomic Docking and WD22TB4 (lp: #1949412).
  * change debhelper verson to 12 so we can build in impish.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Tue, 08 Feb 2022 14:19:55 +0100

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for fwupd has completed successfully and the package is now being 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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwupd - 1.7.5-3~20.04.1

---------------
fwupd (1.7.5-3~20.04.1) focal; urgency=medium

  * Backport 1.7.5-3 from jammy to focal.
  * Support several new devices (LP: #1949412, LP: #1954965, LP: #1953573)
  * fwupd / fwupd-efi source package split (LP: #1955386)
  * Don't install new fwupd-unsiged by default. (LP: #1960783)
  * Disable flashrom in focal as it was not enabled in focal.
  * Downgrade libgusb from 0.3.5 to 0.3.4 which used in focal after
    checking through all commits between. Just what we did on previous
    focal version 1.5.11.

 -- Yuan-Chen Cheng <email address hidden> Mon, 21 Feb 2022 11:06:00 +0800

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwupd-efi - 1:1.2-2~20.04.1

---------------
fwupd-efi (1:1.2-2~20.04.1) focal; urgency=medium

  [ Yuan-Chen Cheng ]
  * Upload as par of the new fwupd 1.7 serie SRU, needed for hardware
    as the Dell's new Atomic Docking and WD22TB4 (lp: #1949412).
  * change debhelper verson to 12 so we can build in focal.

 -- Łukasz 'sil2100' Zemczak <email address hidden> Tue, 08 Feb 2022 14:19:55 +0100

[Launchpad Janitor (janitor)]

This bug was fixed in the package fwupd-signed - 1.27.1ubuntu7

---------------
fwupd-signed (1.27.1ubuntu7) focal; urgency=medium

  * remove fwupd-unsigned from the Recommends of fwupd-signed.
    This is backported from v1.43 (LP: #1960783)

 -- Yuan-Chen Cheng <email address hidden> Wed, 16 Feb 2022 19:14:12 +0800

[Brian Murray (brian-murray)]

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release.