efibootmgr -v UiAppCould not parse device path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
efivar (Debian) |
Fix Released
|
Unknown
|
|||
efivar (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On Eoan, efibootmgr -v output fails with error "UiAppCound not parse device path"; this succeeds on Disco and Bionic.
root@ubuntu:/# efivar --name 8be4df61-
GUID: 8be4df61-
Name: "Boot0000"
Attributes:
Boot Service Access
Runtime Service Access
Value:
00000000 09 01 00 00 2c 00 55 00 69 00 41 00 70 00 70 00 |....,.U.i.A.p.p.|
00000010 00 00 04 07 14 00 c9 bd b8 7c eb f8 34 4f aa ea |.........|..4O..|
00000020 3e e4 af 65 16 a1 04 06 14 00 21 aa 2c 46 14 76 |>..e......!.,F.v|
00000030 03 45 83 6e 8a b6 f4 66 23 31 7f ff 04 00 |.E.n...f#1.... |
root@ubuntu:/# efibootmgr -v
Timeout: 0 seconds
BootOrder: 0000
Boot0000* UiAppCould not parse device path: Invalid argument
Package versions in Eoan, kernel 5.3.0-10-generic
ii efibootmgr 15-1
ii grub-common 2.04-1ubuntu5
ii grub-efi-amd64 2.04-1ubuntu5
ii grub-efi-amd64-bin 2.04-1ubuntu5
ii grub-efi-
ii grub2-common 2.04-1ubuntu5
ii libefiboot1 37-2ubuntu1
ii libefivar1 37-2ubuntu1
Package versions in Disco, kernel 5.0.0-27-generic
ii efibootmgr 15-1
ii grub-common 2.02+dfsg1-
ii grub-efi-amd64 2.02+dfsg1-
ii grub-efi-amd64-bin 2.02+dfsg1-
ii grub-efi-
ii grub2-common 2.02+dfsg1-
ii libefiboot1 37-2
ii libefivar1 37-2
tags: | added: rls-ee-incoming |
affects: | efibootmgr (Ubuntu) → efivar (Ubuntu) |
Changed in efivar (Debian): | |
status: | Unknown → Confirmed |
Changed in efivar (Debian): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.