[Bug 1929471] [NEW] Shim apparently fails to run fwupd64 (hirsute regression?)

[Eugene Crosser]

Public bug reported:

I am running hirsute on Thinkpad X1 Carbon gen 7. Fwupdmgr used to work
on groovy. Now, fwupdmgr detects new firmware, successfully places the
.cap file in /boot/efi/EFI/ubuntu/fw/, successfully sets efi "next boot"
to 2 which is "Linux-Firmware-Updater", but on reboot, there are no
signs that fwupdx64 was attempted to be executed, and system drops
directly into grub.

Same when I use BIOS boot menu. There are entries for "ubuntu" and for
"Linux firmware updater", but selecting any of them boots grub.

After boot, EFI "BootCurrent" points to the updater entry, though it
apparently did not run!

$ efibootmgr -v|head
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0001,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023,0024,0002
Boot0001* ubuntu	HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0002* Linux-Firmware-Updater	HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.d.x.6.4...e.f.i...
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Regulatory Information	FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)

These sympptoms match precisely a previous bug:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1864223

Could it be that the fix introduced then was lost, maybe due to signing
schedule?

There is a github ticket https://github.com/fwupd/firmware-lenovo-
thinkpad/issues/123 that could be explained by this problem too.

My versions of related packages:

shim-signed:
  Installed: 1.47+15.4-0ubuntu2

fwupd-signed:
  Installed: 1.38+1.5.8-0ubuntu1

grub-efi-amd64-signed:
  Installed: 1.169+2.04-1ubuntu45

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: shim-signed 1.47+15.4-0ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon May 24 23:28:40 2021
InstallationDate: Installed on 2020-01-02 (508 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
SecureBoot: 6   0   0   0   1
SourcePackage: shim-signed
UpgradeStatus: Upgraded to hirsute on 2021-02-22 (91 days ago)

** Affects: shim-signed (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug hirsute wayland-session

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

Title:
  Shim apparently fails to run fwupd64 (hirsute regression?)

Status in shim-signed package in Ubuntu:
  New

Bug description:
  I am running hirsute on Thinkpad X1 Carbon gen 7. Fwupdmgr used to
  work on groovy. Now, fwupdmgr detects new firmware, successfully
  places the .cap file in /boot/efi/EFI/ubuntu/fw/, successfully sets
  efi "next boot" to 2 which is "Linux-Firmware-Updater", but on reboot,
  there are no signs that fwupdx64 was attempted to be executed, and
  system drops directly into grub.

  Same when I use BIOS boot menu. There are entries for "ubuntu" and for
  "Linux firmware updater", but selecting any of them boots grub.

  After boot, EFI "BootCurrent" points to the updater entry, though it
  apparently did not run!

  $ efibootmgr -v|head
  BootCurrent: 0002
  Timeout: 0 seconds
  BootOrder: 0001,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023,0024,0002
  Boot0001* ubuntu	HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
  Boot0002* Linux-Firmware-Updater	HD(1,GPT,6ccce482-e2c2-48ca-991e-608bee5d38af,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)\.f.w.u.p.d.x.6.4...e.f.i...
  Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
  Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
  Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
  Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
  Boot0014  Regulatory Information	FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)

  These sympptoms match precisely a previous bug:
  https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1864223

  Could it be that the fix introduced then was lost, maybe due to
  signing schedule?

  There is a github ticket https://github.com/fwupd/firmware-lenovo-
  thinkpad/issues/123 that could be explained by this problem too.

  My versions of related packages:

  shim-signed:
    Installed: 1.47+15.4-0ubuntu2

  fwupd-signed:
    Installed: 1.38+1.5.8-0ubuntu1

  grub-efi-amd64-signed:
    Installed: 1.169+2.04-1ubuntu45

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: shim-signed 1.47+15.4-0ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled'
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 24 23:28:40 2021
  InstallationDate: Installed on 2020-01-02 (508 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  SecureBoot: 6   0   0   0   1
  SourcePackage: shim-signed
  UpgradeStatus: Upgraded to hirsute on 2021-02-22 (91 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1929471/+subscriptions