| 2021-05-24 21:43:02 |
Eugene Crosser |
bug |
|
|
added bug |
| 2021-05-25 15:14:46 |
Launchpad Janitor |
shim-signed (Ubuntu): status |
New |
Confirmed |
|
| 2021-05-28 16:57:34 |
Brian Murray |
tags |
amd64 apport-bug hirsute wayland-session |
amd64 apport-bug hirsute rls-hh-incoming wayland-session |
|
| 2021-06-01 22:23:06 |
Steve Langasek |
bug task added |
|
fwupd (Ubuntu) |
|
| 2021-06-02 02:52:21 |
Launchpad Janitor |
fwupd (Ubuntu): status |
New |
Confirmed |
|
| 2021-06-02 12:34:42 |
Alex Murray |
bug |
|
|
added subscriber Alex Murray |
| 2021-06-03 15:11:08 |
Matthieu Clemenceau |
tags |
amd64 apport-bug hirsute rls-hh-incoming wayland-session |
amd64 apport-bug fr-1424 hirsute rls-hh-incoming wayland-session |
|
| 2021-06-03 16:24:04 |
Brian Murray |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-06-03 16:24:04 |
Brian Murray |
bug task added |
|
shim-signed (Ubuntu Hirsute) |
|
| 2021-06-03 16:24:04 |
Brian Murray |
bug task added |
|
fwupd (Ubuntu Hirsute) |
|
| 2021-06-03 16:24:20 |
Brian Murray |
tags |
amd64 apport-bug fr-1424 hirsute rls-hh-incoming wayland-session |
amd64 apport-bug fr-1424 hirsute wayland-session |
|
| 2021-06-07 15:34:15 |
Steve Langasek |
shim-signed (Ubuntu): status |
Confirmed |
In Progress |
|
| 2021-06-07 15:34:17 |
Steve Langasek |
shim-signed (Ubuntu Hirsute): status |
New |
In Progress |
|
| 2021-06-07 15:37:32 |
Julian Andres Klode |
bug task added |
|
shim (Ubuntu) |
|
| 2021-06-07 15:37:41 |
Julian Andres Klode |
shim (Ubuntu): status |
New |
Fix Committed |
|
| 2021-06-08 16:36:40 |
Mario Limonciello |
fwupd (Ubuntu): status |
Confirmed |
Invalid |
|
| 2021-06-08 16:36:43 |
Mario Limonciello |
fwupd (Ubuntu Hirsute): status |
New |
Invalid |
|
| 2021-06-09 09:04:18 |
Julian Andres Klode |
shim (Ubuntu): status |
Fix Committed |
In Progress |
|
| 2021-06-24 09:17:57 |
Yuan-Chen Cheng |
bug |
|
|
added subscriber Yuan-Chen Cheng |
| 2021-06-24 09:32:36 |
Iain Lane |
bug |
|
|
added subscriber Iain Lane |
| 2021-07-02 19:06:29 |
Launchpad Janitor |
shim (Ubuntu Hirsute): status |
New |
Confirmed |
|
| 2021-07-14 21:12:04 |
Markus Wagner |
bug |
|
|
added subscriber Markus Wagner |
| 2021-07-15 11:32:00 |
Launchpad Janitor |
shim (Ubuntu): status |
In Progress |
Fix Released |
|
| 2021-07-16 09:58:28 |
Julian Andres Klode |
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) |
[Impact]
fwupd does not load, can't upgrade firmware
[Test case]
Try reinstall a firmware upgrade, make sure fwupd loads. Make sure you use secure boot. It's OK testing this in one release, as the fix is entirely shim-side and it's binary-copied.
[Where problems could occur]
We might fail to load fwupd on other systems. There should be no problem loading grub, as shim will always fall back to it if it can't load a specified boot loader.
[Original bug report]
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) |
|
| 2021-07-16 09:58:40 |
Julian Andres Klode |
description |
[Impact]
fwupd does not load, can't upgrade firmware
[Test case]
Try reinstall a firmware upgrade, make sure fwupd loads. Make sure you use secure boot. It's OK testing this in one release, as the fix is entirely shim-side and it's binary-copied.
[Where problems could occur]
We might fail to load fwupd on other systems. There should be no problem loading grub, as shim will always fall back to it if it can't load a specified boot loader.
[Original bug report]
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) |
[Impact]
fwupd does not load, can't upgrade firmware
[Test plan]
Try reinstall a firmware upgrade, make sure fwupd loads. Make sure you use secure boot. It's OK testing this in one release, as the fix is entirely shim-side and it's binary-copied.
[Where problems could occur]
We might fail to load fwupd on other systems. There should be no problem loading grub, as shim will always fall back to it if it can't load a specified boot loader.
[Original bug report]
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) |
|
| 2021-07-16 10:45:30 |
Launchpad Janitor |
shim-signed (Ubuntu): status |
In Progress |
Fix Released |
|
| 2021-07-16 15:11:22 |
Łukasz Zemczak |
shim (Ubuntu Hirsute): status |
Confirmed |
Fix Committed |
|
| 2021-07-16 15:11:24 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-07-16 15:11:26 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2021-07-16 15:11:29 |
Łukasz Zemczak |
tags |
amd64 apport-bug fr-1424 hirsute wayland-session |
amd64 apport-bug fr-1424 hirsute verification-needed verification-needed-hirsute wayland-session |
|
| 2021-07-16 15:22:26 |
Łukasz Zemczak |
shim (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-07-16 15:22:30 |
Łukasz Zemczak |
tags |
amd64 apport-bug fr-1424 hirsute verification-needed verification-needed-hirsute wayland-session |
amd64 apport-bug fr-1424 hirsute verification-needed verification-needed-focal verification-needed-hirsute wayland-session |
|
| 2021-07-16 16:07:37 |
Łukasz Zemczak |
shim-signed (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2021-07-16 20:26:44 |
Eugene Crosser |
tags |
amd64 apport-bug fr-1424 hirsute verification-needed verification-needed-focal verification-needed-hirsute wayland-session |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-needed verification-needed-focal wayland-session |
|
| 2021-07-19 11:55:24 |
Łukasz Zemczak |
shim-signed (Ubuntu Hirsute): status |
In Progress |
Fix Committed |
|
| 2021-07-19 12:02:49 |
Łukasz Zemczak |
shim (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2021-07-19 12:02:55 |
Łukasz Zemczak |
tags |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-needed verification-needed-focal wayland-session |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal wayland-session |
|
| 2021-07-19 12:23:05 |
Łukasz Zemczak |
shim-signed (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2021-07-19 12:26:40 |
Łukasz Zemczak |
shim (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2021-07-19 12:26:45 |
Łukasz Zemczak |
tags |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal wayland-session |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial wayland-session |
|
| 2021-07-19 12:35:59 |
Łukasz Zemczak |
shim-signed (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2021-07-22 10:12:29 |
Pavol Pitonak |
bug |
|
|
added subscriber Pavol Pitonak |
| 2021-07-23 13:23:13 |
Julian Andres Klode |
tags |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-needed verification-needed-bionic verification-needed-focal verification-needed-xenial wayland-session |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-done-xenial verification-needed verification-needed-bionic verification-needed-focal wayland-session |
|
| 2021-07-23 16:06:19 |
Julian Andres Klode |
tags |
amd64 apport-bug fr-1424 hirsute verification-done-hirsute verification-done-xenial verification-needed verification-needed-bionic verification-needed-focal wayland-session |
amd64 apport-bug fr-1424 hirsute verification-done verification-done-bionic verification-done-focal verification-done-hirsute verification-done-xenial wayland-session |
|
| 2021-07-26 08:18:30 |
Julian Andres Klode |
description |
[Impact]
fwupd does not load, can't upgrade firmware
[Test plan]
Try reinstall a firmware upgrade, make sure fwupd loads. Make sure you use secure boot. It's OK testing this in one release, as the fix is entirely shim-side and it's binary-copied.
[Where problems could occur]
We might fail to load fwupd on other systems. There should be no problem loading grub, as shim will always fall back to it if it can't load a specified boot loader.
[Original bug report]
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) |
[Impact]
fwupd does not load, can't upgrade firmware
[Test plan]
Try reinstall a firmware upgrade, make sure fwupd loads. Make sure you use secure boot. It's OK testing this in one release, as the fix is entirely shim-side and it's binary-copied.
[Where problems could occur]
We might fail to boot from BIOS generated boot entries, as in 1937115
[Original bug report]
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) |
|
| 2021-07-26 08:18:54 |
Julian Andres Klode |
description |
[Impact]
fwupd does not load, can't upgrade firmware
[Test plan]
Try reinstall a firmware upgrade, make sure fwupd loads. Make sure you use secure boot. It's OK testing this in one release, as the fix is entirely shim-side and it's binary-copied.
[Where problems could occur]
We might fail to boot from BIOS generated boot entries, as in 1937115
[Original bug report]
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) |
[Impact]
fwupd does not load, can't upgrade firmware
[Test plan]
Try reinstall a firmware upgrade, make sure fwupd loads. Make sure you use secure boot. It's OK testing this in one release, as the fix is entirely shim-side and it's binary-copied.
[Where problems could occur]
We might fail to boot from BIOS generated boot entries, as in bug 1937115
[Original bug report]
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) |
|
| 2021-07-27 09:19:04 |
Launchpad Janitor |
shim-signed (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-07-27 09:19:15 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-07-27 09:22:43 |
Launchpad Janitor |
shim (Ubuntu Hirsute): status |
Fix Committed |
Fix Released |
|
| 2021-08-02 19:46:11 |
Launchpad Janitor |
shim (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-08-02 19:46:16 |
Launchpad Janitor |
shim-signed (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-08-16 10:30:11 |
Launchpad Janitor |
shim (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2021-08-16 10:30:18 |
Launchpad Janitor |
shim-signed (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2021-09-07 08:20:12 |
Launchpad Janitor |
shim (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2021-09-07 08:20:35 |
Launchpad Janitor |
shim-signed (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2021-10-03 09:22:35 |
Mathew Hodson |
bug task deleted |
fwupd (Ubuntu Hirsute) |
|
|
| 2021-10-03 09:22:43 |
Mathew Hodson |
bug task deleted |
fwupd (Ubuntu) |
|
|
| 2021-12-06 12:57:13 |
Dennis Schridde |
bug |
|
|
added subscriber Dennis Schridde |
| 2021-12-06 12:57:34 |
Dennis Schridde |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=2029396 |
|
| 2021-12-06 12:57:34 |
Dennis Schridde |
bug task added |
|
shim (Fink) |
|
| 2021-12-06 12:57:52 |
Dennis Schridde |
bug task deleted |
shim (Fink) |
|
|
| 2021-12-06 12:58:04 |
Dennis Schridde |
bug task added |
|
shim (Fedora) |
|
| 2021-12-06 13:36:37 |
Bug Watch Updater |
shim (Fedora): status |
Unknown |
Confirmed |
|
| 2021-12-06 13:36:37 |
Bug Watch Updater |
shim (Fedora): importance |
Unknown |
Undecided |
|
| 2021-12-06 13:36:40 |
Bug Watch Updater |
bug watch added |
|
https://github.com/fwupd/firmware-lenovo-thinkpad/issues/123 |
|
| 2021-12-07 13:44:27 |
Bug Watch Updater |
shim (Fedora): status |
Confirmed |
Unknown |
|
