| 2019-08-17 23:29:28 |
Luis Alberto Pabón |
bug |
|
|
added bug |
| 2019-09-16 15:17:22 |
Launchpad Janitor |
grub2-signed (Ubuntu): status |
New |
Confirmed |
|
| 2019-12-06 21:05:35 |
Christopher C. LaFrancis |
bug |
|
|
added subscriber Christopher C. LaFrancis |
| 2020-02-06 08:07:57 |
henry2man |
bug |
|
|
added subscriber henry2man |
| 2020-02-21 19:10:49 |
Thomas Piekarski |
bug |
|
|
added subscriber Thomas Piekarski |
| 2020-02-24 16:41:51 |
Thomas Piekarski |
grub2-signed (Ubuntu): assignee |
|
Thomas Piekarski (t-piekarski) |
|
| 2020-03-03 20:31:58 |
Guilherme G. Piccoli |
bug |
|
|
added subscriber Guilherme G. Piccoli |
| 2020-03-19 09:06:40 |
Neil Vergottini |
bug |
|
|
added subscriber Neil Vergottini |
| 2020-03-25 19:12:57 |
Blastoff |
bug |
|
|
added subscriber Blastoff |
| 2020-03-27 06:46:11 |
Thomas Piekarski |
grub2-signed (Ubuntu): assignee |
Thomas Piekarski (t-piekarski) |
|
|
| 2020-03-28 02:05:50 |
Cédric Martineau |
bug |
|
|
added subscriber Cédric Martineau |
| 2020-03-30 17:56:05 |
paul-lawrenceville |
bug |
|
|
added subscriber paul-lawrenceville |
| 2020-03-31 16:47:19 |
Andreas Hasenack |
bug |
|
|
added subscriber Andreas Hasenack |
| 2020-05-25 20:52:15 |
Sander van Zoest |
bug |
|
|
added subscriber Sander van Zoest |
| 2020-08-19 17:46:19 |
Rafael Jesus Alcantara Perez |
bug |
|
|
added subscriber Rafael Jesus Alcantara Perez |
| 2020-10-07 03:10:06 |
Brett Frankenberger |
bug |
|
|
added subscriber Brett Frankenberger |
| 2021-01-21 21:38:56 |
Matthew Ruffell |
bug |
|
|
added subscriber Matthew Ruffell |
| 2021-03-22 18:51:42 |
Janåke Rönnblom |
bug |
|
|
added subscriber Janåke Rönnblom |
| 2021-07-08 23:33:27 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Ubuntu) |
|
| 2021-07-08 23:33:37 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu): status |
New |
In Progress |
|
| 2021-07-08 23:33:43 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu): importance |
Undecided |
Medium |
|
| 2021-07-08 23:33:46 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2021-07-08 23:33:50 |
Mauricio Faria de Oliveira |
grub2-signed (Ubuntu): status |
Confirmed |
Invalid |
|
| 2021-07-08 23:34:03 |
Mauricio Faria de Oliveira |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990836 |
|
| 2021-07-08 23:34:03 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Debian) |
|
| 2021-07-08 23:34:34 |
Mauricio Faria de Oliveira |
tags |
amd64 apport-bug disco wayland-session |
amd64 apport-bug disco sts wayland-session |
|
| 2021-07-09 00:51:35 |
Bug Watch Updater |
grub2 (Debian): status |
Unknown |
New |
|
| 2021-07-21 09:04:21 |
George L. Yermulnik |
bug |
|
|
added subscriber George L. Yermulnik |
| 2021-07-22 22:21:17 |
Mauricio Faria de Oliveira |
description |
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* Users on non-pc/i386 platforms (e.g., efi/amd64) may observe
the message "error: can't find command `hwmatch'" every boot.
* Also observed on cloud instances, generating support tickets
asking for clarification/impacts. (which could be deflected.)
* There' little or no impact, as hwmatch is only used to check
hardware device ID against a list for issues w/ graphics/KMS.
When this error happens, the default is set to keep graphics.
* This has possibly always happened on non-pc/i386, as hwmatch
is patched/exists only in 'grub-core/commands/_i386/pc_' dir,
thus there doesn't seem to be any serious issues as a result.
[Fix]
* Check for `$grub_platform != pc` then do not call hwmatch;
just keep current behavior (ie, keep graphics/framebuffer.)
[Test Plan]
* Boot a VM with EFI (e.g., multipass/libvirt/ovmf) and see
the serial console show the error message (or not, w/ fix.)
sudo snap install multipass
sudo multipass set local.driver=libvirt
sudo snap connect multipass:libvirt
multipass launch -c 1 -d 4g -m 1g -n hwmatch-i daily:impish
sudo apt -y install ovmf
sudo mkdir -p /var/lib/libvirt/qemu/nvram
virsh edit hwmatch-i
# insert in <os> section:
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/hwmatch-i.fd</nvram>
virsh shutdown hwmatch-i
virsh start --console hwmatch-i
* Before:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
error: can't find command `hwmatch'.
[ 0.000000] Linux version ...
* After:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
[ 0.000000] Linux version ...
[Where problems could occur]
* Issues with graphics/flickering during boot on systems with
graphics adapters in use might be hit in case of regression.
* Theoretically the risk is low, since hwmatch apparently has
never worked on non-pc/i386, and we replace the broken call
while keeping current behavior observed with it ("no change".)
[Other Info]
* While it might be interesting to try and enable/fix it for
other platforms, let's have a trivial fix to be considered
to backport to stable releases, at this time (less changes.)
* The same behavior is linux_gfx_mode=keep, despite the error.
This happens because in the error case, grub shell evaluates
if hwmatch ...; then` to true, and `if [ $match = 0 ]; then`
to true too (as it's undefined) so `set linux_gfx_mode=keep`.
Before/After in grub shell (same behavior):
grub> hwmatch
error: can't find command `hwmatch'.
grub> echo $grub_platform
efi
grub> echo $linux_gfx_mode
keep
* Other details in Debian bug 990836 [1].
* It looks like grub2-unsigned follows grub2 automatically,
so not providing debdiffs to it/just grub2.
[Links]
* [1] https://bugs.debian.org/990836
[Original Description]
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2021-07-22 22:22:57 |
Mauricio Faria de Oliveira |
attachment added |
|
lp1840560_grub2_impish.debdiff https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1840560/+attachment/5512983/+files/lp1840560_grub2_impish.debdiff |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Groovy |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Ubuntu Groovy) |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2-signed (Ubuntu Groovy) |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Hirsute |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Ubuntu Hirsute) |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2-signed (Ubuntu Hirsute) |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Focal |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Ubuntu Focal) |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2-signed (Ubuntu Focal) |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Impish |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Ubuntu Impish) |
|
| 2021-07-22 22:23:52 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2-signed (Ubuntu Impish) |
|
| 2021-07-22 22:24:17 |
Mauricio Faria de Oliveira |
grub2-signed (Ubuntu Hirsute): status |
New |
Invalid |
|
| 2021-07-22 22:24:26 |
Mauricio Faria de Oliveira |
grub2-signed (Ubuntu Groovy): status |
New |
Invalid |
|
| 2021-07-22 22:24:35 |
Mauricio Faria de Oliveira |
grub2-signed (Ubuntu Focal): status |
New |
Invalid |
|
| 2021-07-22 22:25:01 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Hirsute): status |
New |
In Progress |
|
| 2021-07-22 22:25:13 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Hirsute): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2021-07-22 22:25:22 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Groovy): status |
New |
Invalid |
|
| 2021-07-22 22:25:37 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-07-22 22:25:37 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Focal): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2021-07-22 22:26:19 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Impish): importance |
Medium |
Low |
|
| 2021-07-22 22:26:29 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Hirsute): importance |
Undecided |
Low |
|
| 2021-07-22 22:26:39 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Focal): importance |
Undecided |
Low |
|
| 2021-07-22 22:32:57 |
Mauricio Faria de Oliveira |
description |
[Impact]
* Users on non-pc/i386 platforms (e.g., efi/amd64) may observe
the message "error: can't find command `hwmatch'" every boot.
* Also observed on cloud instances, generating support tickets
asking for clarification/impacts. (which could be deflected.)
* There' little or no impact, as hwmatch is only used to check
hardware device ID against a list for issues w/ graphics/KMS.
When this error happens, the default is set to keep graphics.
* This has possibly always happened on non-pc/i386, as hwmatch
is patched/exists only in 'grub-core/commands/_i386/pc_' dir,
thus there doesn't seem to be any serious issues as a result.
[Fix]
* Check for `$grub_platform != pc` then do not call hwmatch;
just keep current behavior (ie, keep graphics/framebuffer.)
[Test Plan]
* Boot a VM with EFI (e.g., multipass/libvirt/ovmf) and see
the serial console show the error message (or not, w/ fix.)
sudo snap install multipass
sudo multipass set local.driver=libvirt
sudo snap connect multipass:libvirt
multipass launch -c 1 -d 4g -m 1g -n hwmatch-i daily:impish
sudo apt -y install ovmf
sudo mkdir -p /var/lib/libvirt/qemu/nvram
virsh edit hwmatch-i
# insert in <os> section:
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/hwmatch-i.fd</nvram>
virsh shutdown hwmatch-i
virsh start --console hwmatch-i
* Before:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
error: can't find command `hwmatch'.
[ 0.000000] Linux version ...
* After:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
[ 0.000000] Linux version ...
[Where problems could occur]
* Issues with graphics/flickering during boot on systems with
graphics adapters in use might be hit in case of regression.
* Theoretically the risk is low, since hwmatch apparently has
never worked on non-pc/i386, and we replace the broken call
while keeping current behavior observed with it ("no change".)
[Other Info]
* While it might be interesting to try and enable/fix it for
other platforms, let's have a trivial fix to be considered
to backport to stable releases, at this time (less changes.)
* The same behavior is linux_gfx_mode=keep, despite the error.
This happens because in the error case, grub shell evaluates
if hwmatch ...; then` to true, and `if [ $match = 0 ]; then`
to true too (as it's undefined) so `set linux_gfx_mode=keep`.
Before/After in grub shell (same behavior):
grub> hwmatch
error: can't find command `hwmatch'.
grub> echo $grub_platform
efi
grub> echo $linux_gfx_mode
keep
* Other details in Debian bug 990836 [1].
* It looks like grub2-unsigned follows grub2 automatically,
so not providing debdiffs to it/just grub2.
[Links]
* [1] https://bugs.debian.org/990836
[Original Description]
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* Users on non-pc/i386 platforms (e.g., efi/amd64) may observe
the message "error: can't find command `hwmatch'" every boot.
* Also observed on cloud instances, generating support tickets
asking for clarification/impacts. (which could be deflected.)
* There' little or no impact, as hwmatch is only used to check
hardware device ID against a list for issues w/ graphics/KMS.
When this error happens, the default is set to keep graphics.
* This has possibly always happened on non-pc/i386, as hwmatch
is patched/exists only in 'grub-core/commands/_i386/pc_' dir,
thus there doesn't seem to be any serious issues as a result.
[Fix]
* Check for `$grub_platform != pc` then do not call hwmatch;
just keep current behavior (ie, keep graphics/framebuffer.)
[Test Plan]
* Boot a VM with EFI (e.g., multipass/libvirt/ovmf) and see
the serial console show the error message (or not, w/ fix.)
sudo snap install multipass
sudo multipass set local.driver=libvirt
sudo snap connect multipass:libvirt
multipass launch -c 1 -d 4g -m 1g -n hwmatch-i daily:impish
sudo apt -y install ovmf
sudo mkdir -p /var/lib/libvirt/qemu/nvram
virsh edit hwmatch-i
# insert in <os> section:
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/hwmatch-i.fd</nvram>
virsh shutdown hwmatch-i
virsh start --console hwmatch-i
* Before:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
error: can't find command `hwmatch'.
[ 0.000000] Linux version ...
* After: (installing grub-common_*.deb is enough to test.)
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
[ 0.000000] Linux version ...
[Where problems could occur]
* Issues with graphics/flickering during boot on systems with
graphics adapters in use might be hit in case of regression.
* Theoretically the risk is low, since hwmatch apparently has
never worked on non-pc/i386, and we replace the broken call
while keeping current behavior observed with it ("no change".)
[Other Info]
* While it might be interesting to try and enable/fix it for
other platforms, let's have a trivial fix to be considered
to backport to stable releases, at this time (less changes.)
* The same behavior is linux_gfx_mode=keep, despite the error.
This happens because in the error case, grub shell evaluates
if hwmatch ...; then` to true, and `if [ $match = 0 ]; then`
to true too (as it's undefined) so `set linux_gfx_mode=keep`.
Before/After in grub shell (same behavior):
grub> hwmatch
error: can't find command `hwmatch'.
grub> echo $grub_platform
efi
grub> echo $linux_gfx_mode
keep
* Other details in Debian bug 990836 [1].
* It looks like grub2-unsigned follows grub2 automatically,
so not providing debdiffs to it/just grub2.
[Links]
* [1] https://bugs.debian.org/990836
[Original Description]
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2021-07-22 22:35:02 |
Mauricio Faria de Oliveira |
description |
[Impact]
* Users on non-pc/i386 platforms (e.g., efi/amd64) may observe
the message "error: can't find command `hwmatch'" every boot.
* Also observed on cloud instances, generating support tickets
asking for clarification/impacts. (which could be deflected.)
* There' little or no impact, as hwmatch is only used to check
hardware device ID against a list for issues w/ graphics/KMS.
When this error happens, the default is set to keep graphics.
* This has possibly always happened on non-pc/i386, as hwmatch
is patched/exists only in 'grub-core/commands/_i386/pc_' dir,
thus there doesn't seem to be any serious issues as a result.
[Fix]
* Check for `$grub_platform != pc` then do not call hwmatch;
just keep current behavior (ie, keep graphics/framebuffer.)
[Test Plan]
* Boot a VM with EFI (e.g., multipass/libvirt/ovmf) and see
the serial console show the error message (or not, w/ fix.)
sudo snap install multipass
sudo multipass set local.driver=libvirt
sudo snap connect multipass:libvirt
multipass launch -c 1 -d 4g -m 1g -n hwmatch-i daily:impish
sudo apt -y install ovmf
sudo mkdir -p /var/lib/libvirt/qemu/nvram
virsh edit hwmatch-i
# insert in <os> section:
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/hwmatch-i.fd</nvram>
virsh shutdown hwmatch-i
virsh start --console hwmatch-i
* Before:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
error: can't find command `hwmatch'.
[ 0.000000] Linux version ...
* After: (installing grub-common_*.deb is enough to test.)
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
[ 0.000000] Linux version ...
[Where problems could occur]
* Issues with graphics/flickering during boot on systems with
graphics adapters in use might be hit in case of regression.
* Theoretically the risk is low, since hwmatch apparently has
never worked on non-pc/i386, and we replace the broken call
while keeping current behavior observed with it ("no change".)
[Other Info]
* While it might be interesting to try and enable/fix it for
other platforms, let's have a trivial fix to be considered
to backport to stable releases, at this time (less changes.)
* The same behavior is linux_gfx_mode=keep, despite the error.
This happens because in the error case, grub shell evaluates
if hwmatch ...; then` to true, and `if [ $match = 0 ]; then`
to true too (as it's undefined) so `set linux_gfx_mode=keep`.
Before/After in grub shell (same behavior):
grub> hwmatch
error: can't find command `hwmatch'.
grub> echo $grub_platform
efi
grub> echo $linux_gfx_mode
keep
* Other details in Debian bug 990836 [1].
* It looks like grub2-unsigned follows grub2 automatically,
so not providing debdiffs to it/just grub2.
[Links]
* [1] https://bugs.debian.org/990836
[Original Description]
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* Users on non-pc/i386 platforms (e.g., efi/amd64) may observe
the message "error: can't find command `hwmatch'" every boot.
* Also observed on cloud instances, generating support tickets
asking for clarification/impacts. (which could be deflected.)
* There' little or no impact, as hwmatch is only used to check
hardware device ID against a list for issues w/ graphics/KMS.
When this error happens, the default is set to keep graphics.
* This has possibly always happened on non-pc/i386, as hwmatch
is patched/exists only in 'grub-core/commands/_i386/pc_' dir,
thus there doesn't seem to be any serious issues as a result.
[Fix]
* Check for `$grub_platform != pc` then do not call hwmatch;
just keep current behavior (ie, keep graphics/framebuffer.)
[Test Plan]
* Boot a VM with EFI (e.g., multipass/libvirt/ovmf) and see
the serial console show the error message (or not, w/ fix.)
sudo snap install multipass
sudo multipass set local.driver=libvirt
sudo snap connect multipass:libvirt
multipass launch -c 1 -d 4g -m 1g -n hwmatch-i daily:impish
sudo apt -y install ovmf
sudo mkdir -p /var/lib/libvirt/qemu/nvram
virsh edit hwmatch-i
# insert in <os> section:
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/hwmatch-i.fd</nvram>
virsh shutdown hwmatch-i
virsh start --console hwmatch-i
* Before:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
error: can't find command `hwmatch'.
[ 0.000000] Linux version ...
* After:
sudo dpkg -i grub_common_*.deb # test package; g-c is enough.
sudo update-grub && sudo reboot
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
[ 0.000000] Linux version ...
[Where problems could occur]
* Issues with graphics/flickering during boot on systems with
graphics adapters in use might be hit in case of regression.
* Theoretically the risk is low, since hwmatch apparently has
never worked on non-pc/i386, and we replace the broken call
while keeping current behavior observed with it ("no change".)
[Other Info]
* While it might be interesting to try and enable/fix it for
other platforms, let's have a trivial fix to be considered
to backport to stable releases, at this time (less changes.)
* The same behavior is linux_gfx_mode=keep, despite the error.
This happens because in the error case, grub shell evaluates
if hwmatch ...; then` to true, and `if [ $match = 0 ]; then`
to true too (as it's undefined) so `set linux_gfx_mode=keep`.
Before/After in grub shell (same behavior):
grub> hwmatch
error: can't find command `hwmatch'.
grub> echo $grub_platform
efi
grub> echo $linux_gfx_mode
keep
* Other details in Debian bug 990836 [1].
* It looks like grub2-unsigned follows grub2 automatically,
so not providing debdiffs to it/just grub2.
[Links]
* [1] https://bugs.debian.org/990836
[Original Description]
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2021-07-23 00:30:35 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-bug disco sts wayland-session |
amd64 apport-bug disco patch sts wayland-session |
|
| 2021-08-20 15:32:19 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mfo/grub/+git/grub/+merge/407470 |
|
| 2021-10-12 02:34:33 |
Ivan D |
bug |
|
|
added subscriber Ivan D |
| 2021-11-04 13:50:13 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Jammy |
|
| 2021-11-04 13:50:13 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Ubuntu Jammy) |
|
| 2021-11-04 13:50:13 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2-signed (Ubuntu Jammy) |
|
| 2021-11-04 13:50:13 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-11-04 13:50:13 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2 (Ubuntu Bionic) |
|
| 2021-11-04 13:50:13 |
Mauricio Faria de Oliveira |
bug task added |
|
grub2-signed (Ubuntu Bionic) |
|
| 2021-11-04 13:50:57 |
Mauricio Faria de Oliveira |
grub2-signed (Ubuntu Bionic): status |
New |
Invalid |
|
| 2021-11-04 13:51:22 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Bionic): status |
New |
In Progress |
|
| 2021-11-04 13:51:36 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Bionic): importance |
Undecided |
Low |
|
| 2021-11-04 13:51:36 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Bionic): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2021-11-19 22:58:22 |
Launchpad Janitor |
grub2 (Ubuntu Jammy): status |
In Progress |
Fix Released |
|
| 2021-11-23 15:16:12 |
Neil Vergottini |
removed subscriber Neil Vergottini |
|
|
|
| 2021-12-02 18:03:51 |
Mauricio Faria de Oliveira |
description |
[Impact]
* Users on non-pc/i386 platforms (e.g., efi/amd64) may observe
the message "error: can't find command `hwmatch'" every boot.
* Also observed on cloud instances, generating support tickets
asking for clarification/impacts. (which could be deflected.)
* There' little or no impact, as hwmatch is only used to check
hardware device ID against a list for issues w/ graphics/KMS.
When this error happens, the default is set to keep graphics.
* This has possibly always happened on non-pc/i386, as hwmatch
is patched/exists only in 'grub-core/commands/_i386/pc_' dir,
thus there doesn't seem to be any serious issues as a result.
[Fix]
* Check for `$grub_platform != pc` then do not call hwmatch;
just keep current behavior (ie, keep graphics/framebuffer.)
[Test Plan]
* Boot a VM with EFI (e.g., multipass/libvirt/ovmf) and see
the serial console show the error message (or not, w/ fix.)
sudo snap install multipass
sudo multipass set local.driver=libvirt
sudo snap connect multipass:libvirt
multipass launch -c 1 -d 4g -m 1g -n hwmatch-i daily:impish
sudo apt -y install ovmf
sudo mkdir -p /var/lib/libvirt/qemu/nvram
virsh edit hwmatch-i
# insert in <os> section:
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/hwmatch-i.fd</nvram>
virsh shutdown hwmatch-i
virsh start --console hwmatch-i
* Before:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
error: can't find command `hwmatch'.
[ 0.000000] Linux version ...
* After:
sudo dpkg -i grub_common_*.deb # test package; g-c is enough.
sudo update-grub && sudo reboot
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
[ 0.000000] Linux version ...
[Where problems could occur]
* Issues with graphics/flickering during boot on systems with
graphics adapters in use might be hit in case of regression.
* Theoretically the risk is low, since hwmatch apparently has
never worked on non-pc/i386, and we replace the broken call
while keeping current behavior observed with it ("no change".)
[Other Info]
* While it might be interesting to try and enable/fix it for
other platforms, let's have a trivial fix to be considered
to backport to stable releases, at this time (less changes.)
* The same behavior is linux_gfx_mode=keep, despite the error.
This happens because in the error case, grub shell evaluates
if hwmatch ...; then` to true, and `if [ $match = 0 ]; then`
to true too (as it's undefined) so `set linux_gfx_mode=keep`.
Before/After in grub shell (same behavior):
grub> hwmatch
error: can't find command `hwmatch'.
grub> echo $grub_platform
efi
grub> echo $linux_gfx_mode
keep
* Other details in Debian bug 990836 [1].
* It looks like grub2-unsigned follows grub2 automatically,
so not providing debdiffs to it/just grub2.
[Links]
* [1] https://bugs.debian.org/990836
[Original Description]
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
[Impact]
* Users on non-pc/i386 platforms (e.g., efi/amd64) may observe
the message "error: can't find command `hwmatch'" every boot.
* Also observed on cloud instances, generating support tickets
asking for clarification/impacts. (which could be deflected.)
* There' little or no impact, as hwmatch is only used to check
hardware device ID against a list for issues w/ graphics/KMS.
When this error happens, the default is set to keep graphics.
* This has possibly always happened on non-pc/i386, as hwmatch
is patched/exists only in 'grub-core/commands/_i386/pc_' dir,
thus there doesn't seem to be any serious issues as a result.
[Fix]
* Check for `$grub_platform != pc` then do not call hwmatch;
just keep current behavior (ie, keep graphics/framebuffer.)
[Test Plan]
* Boot a VM with EFI (LXD or multipass/libvirt/ovmf) and see
the serial console show the error message (or not, w/ fix.)
- lxd:
$ lxc launch ubuntu:impish impish-vm --vm --console
Creating impish-vm
Starting impish-vm
To detach from the console, press: <ctrl>+a q
BdsDxe: loading Boot0001 "UEFI QEMU QEMU HARDDISK " from ...
BdsDxe: starting Boot0001 "UEFI QEMU QEMU HARDDISK " from ...
error: can't find command `hwmatch'.
...
- multipass/libvirt/ovmf:
sudo snap install multipass
sudo multipass set local.driver=libvirt
sudo snap connect multipass:libvirt
multipass launch -c 1 -d 4g -m 1g -n hwmatch-i impish
sudo apt -y install ovmf
sudo mkdir -p /var/lib/libvirt/qemu/nvram
virsh edit hwmatch-i
# insert in <os> section:
<loader readonly='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.fd</loader>
<nvram>/var/lib/libvirt/qemu/nvram/hwmatch-i.fd</nvram>
virsh shutdown hwmatch-i
virsh start --console hwmatch-i
* Before:
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
error: can't find command `hwmatch'.
[ 0.000000] Linux version ...
* After:
sudo dpkg -i grub_common_*.deb # test package; g-c is enough.
sudo update-grub && sudo reboot
...
BdsDxe: loading Boot0003 "ubuntu" from ...\shimx64.efi
BdsDxe: starting Boot0003 "ubuntu" from ...\shimx64.efi
[ 0.000000] Linux version ...
[Where problems could occur]
* Issues with graphics/flickering during boot on systems with
graphics adapters in use might be hit in case of regression.
* Theoretically the risk is low, since hwmatch apparently has
never worked on non-pc/i386, and we replace the broken call
while keeping current behavior observed with it ("no change".)
[Other Info]
* While it might be interesting to try and enable/fix it for
other platforms, let's have a trivial fix to be considered
to backport to stable releases, at this time (less changes.)
* The same behavior is linux_gfx_mode=keep, despite the error.
This happens because in the error case, grub shell evaluates
if hwmatch ...; then` to true, and `if [ $match = 0 ]; then`
to true too (as it's undefined) so `set linux_gfx_mode=keep`.
Before/After in grub shell (same behavior):
grub> hwmatch
error: can't find command `hwmatch'.
grub> echo $grub_platform
efi
grub> echo $linux_gfx_mode
keep
* Other details in Debian bug 990836 [1].
* It looks like grub2-unsigned follows grub2 automatically,
so not providing debdiffs to it/just grub2.
[Links]
* [1] https://bugs.debian.org/990836
[Original Description]
Upon disabling my grub menu using grub-customizer, I've noticed that just before the system boots and goes into the crypto password prompt the following error message appears on the display:
```
error: can't find command hwmatch
```
Looks like this command is referenced from /boot/grub/grub/cfg
```
if hwmatch ${prefix}/gfxblacklist.txt 3; then
```
However, the mod doesn't exist on grub's mod folder:
```
~ ls -la /boot/grub/x86_64-efi/*.mod|wc -l
269
~ ls -la /boot/grub/x86_64-efi/hw*
fish: No matches for wildcard “/boot/grub/x86_64-efi/hw*”
```
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 18 00:22:41 2019
InstallationDate: Installed on 2019-08-17 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub2-signed
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2021-12-02 19:46:04 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~mfo/grub/+git/grub/+merge/412712 |
|
| 2021-12-02 19:58:05 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Bionic): status |
In Progress |
Won't Fix |
|
| 2021-12-02 19:59:04 |
Mauricio Faria de Oliveira |
tags |
amd64 apport-bug disco patch sts wayland-session |
amd64 apport-bug block-proposed-focal block-proposed-hirsute block-proposed-impish disco patch sts wayland-session |
|
| 2022-01-11 16:10:21 |
Julian Andres Klode |
grub2 (Ubuntu Hirsute): status |
In Progress |
Triaged |
|
| 2022-01-11 16:10:30 |
Julian Andres Klode |
grub2 (Ubuntu Impish): status |
In Progress |
Triaged |
|
| 2022-01-11 16:13:15 |
Julian Andres Klode |
grub2 (Ubuntu Hirsute): status |
Triaged |
Won't Fix |
|
| 2022-01-11 16:42:30 |
paul-lawrenceville |
removed subscriber paul-lawrenceville |
|
|
|
| 2022-03-15 15:47:25 |
Julian Andres Klode |
tags |
amd64 apport-bug block-proposed-focal block-proposed-hirsute block-proposed-impish disco patch sts wayland-session |
amd64 apport-bug disco patch sts wayland-session |
|
| 2022-03-22 08:42:58 |
Łukasz Zemczak |
grub2 (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-03-22 08:43:02 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-03-22 08:43:03 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2022-03-22 08:43:09 |
Łukasz Zemczak |
tags |
amd64 apport-bug disco patch sts wayland-session |
amd64 apport-bug disco patch sts verification-needed verification-needed-focal wayland-session |
|
| 2022-03-22 15:14:45 |
Ivan D |
removed subscriber Ivan D |
|
|
|
| 2022-03-22 19:33:33 |
Mauricio Faria de Oliveira |
tags |
amd64 apport-bug disco patch sts verification-needed verification-needed-focal wayland-session |
amd64 apport-bug disco patch sts verification-done verification-done-focal wayland-session |
|
| 2022-03-23 19:46:22 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2022-04-04 07:18:31 |
Launchpad Janitor |
grub2 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-04-04 07:18:38 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-09-14 13:50:20 |
Mauricio Faria de Oliveira |
grub2 (Ubuntu Impish): status |
Triaged |
Won't Fix |
|
| 2023-09-05 16:55:37 |
Bug Watch Updater |
grub2 (Debian): status |
New |
Fix Released |
|
