[Bug 1820768] Re: [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

[Bearsh]

I installed fwupd and fwupd-signed from -proposed and removed fwupdate
as a update for my bios is available I would like to upgrade but:

$ fwupdmgr update 
Downloading 0.2.13.0 for XPS 13 9360 System Firmware...
Decompressing…           [***************************************]
Authenticating…          [***************************************]
Updating XPS 13 9360 System Firmware…                            ]
Scheduling…              [***************************************]
Secure boot is enabled, but shim isn't installed to the EFI system partition
$ efibootmgr 
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000
Boot0000* ubuntu
Boot0006* UEFI: PC300 NVMe SK hynix 512GB, Partition 1

this used to work in the past (I think with fwupd in bionic which an the
other hand started to fail because of other things). or do I have to
install shim manually in some way?

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

Title:
  [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10

Status in OEM Priority Project:
  In Progress
Status in fwupd package in Ubuntu:
  Fix Released
Status in fwupd-signed package in Ubuntu:
  Fix Released
Status in fwupdate package in Ubuntu:
  Fix Released
Status in libxmlb package in Ubuntu:
  Fix Released
Status in fwupd source package in Bionic:
  Fix Committed
Status in fwupd-signed source package in Bionic:
  Fix Committed
Status in fwupdate source package in Bionic:
  Fix Committed
Status in libxmlb source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  Bios vendor is pushing to put the new design into cab file, and also
  new docking DW19 needs the new fwupd to support it.

  That needs new fwupd to support.

  * Background:
   1. most user does firmware update via gnome-software and it talk to fwupd.
   2. only very very limited user will call /usr/bin/fwupdate from the command line.
   3. the new fwupd will need a new fwupd-signed. So we will remove fwupdate-signed.

  * Current test result before we have something in proposed channel:
   1. new fwupd works well with gnome-software, so we should be safe to go.
   2. for those very limited user, they can call /usr/lib/fwupd/fwupdate to replace /usr/bin/fwupdate. so it should be safe to remove fwupdate.

  * Test case

  A.
  1. install the new fwupd, and plugin the new docking - DW19.
  2. fwupdmgr get-devices and check if all internal device can properly show

  B.
  1. If you can get new cab file, try to use fwupdmgr install XX.cab to see if can work properly.

  C.
  1. If you can get a machine that have some firmware update pending, try to go gnome-software, and click refresh with the new fwupd, you should be able to see the pending firmware showed there. Which proves that it can properly be integrated with gnome. (ycheng-twn have a laptop with that condition, and he can verify that one

  D.
  1. Install an 18.04 Ubuntu Desktop system.
  2. Enable bionic-proposed.
  3. Run update-manager.
  4. Ensure that the fwupd and fwupd-signed packages are installed without error.
  5. Ensure that no files or directories from the old fwupdate package are left behind in /boot/efi/EFI/ubuntu, /var/lib/fwupdate, or /var/cache/fwupdate.

  * Regression potential

  Since the upstream maintainer is back up this upgrade, and he also
  works in a major computer vendor and works closely with the BIOS team,
  it should be fairly low risk.

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