Ubuntu
efivar package

efibootmgr -v UiAppCould not parse device path

Bug #1844320 reported by Ryan Harper
34
This bug affects 5 people
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-93ca-11d2-aa0d-00e098032b8c-Boot0000 --print
GUID: 8be4df61-93ca-11d2-aa0d-00e098032b8c
Name: "Boot0000"
Attributes:
        Non-Volatile
        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-amd64-signed 1.121+2.04-1ubuntu5
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-12ubuntu2
ii grub-efi-amd64 2.02+dfsg1-12ubuntu2
ii grub-efi-amd64-bin 2.02+dfsg1-12ubuntu2
ii grub-efi-amd64-signed 1.115+2.02+dfsg1-12ubuntu2
ii grub2-common 2.02+dfsg1-12ubuntu2
ii libefiboot1 37-2
ii libefivar1 37-2

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in efibootmgr (Ubuntu):
status: New → Confirmed
Revision history for this message
Dmitry-a-durnev (dmitry-a-durnev) wrote :

efibootmgr without args lists the boot entries correctly:
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,000E,000F,0002,0003,0004
Boot0000* ubuntu
Boot0001* Windows Boot Manager
...
, but

efiboomgr -v

returns:

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,000E,000F,0002,0003,0004
Boot0000* ubuntuCould not parse device path: Invalid argument

So it seems it fails on the first 'ubuntu' entry (which is the currently booted OS) or the 2nd Boot0001 Windows Boot Manager entry - which BTW fails to boot from GRUB (chainloader) for me...

Ryan Harper (raharper)
tags: added: rls-ee-incoming
Michael Hudson-Doyle (mwhudson)
affects: efibootmgr (Ubuntu) → efivar (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package efivar - 37-2ubuntu2

---------------
efivar (37-2ubuntu2) eoan; urgency=medium

  * Backport more fixes from upstream that fix efibootmgr -v. (LP: #1844320)

 -- Michael Hudson-Doyle <email address hidden> Wed, 25 Sep 2019 10:50:57 +1200

Changed in efivar (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Ryan Harper (raharper) wrote :

Thanks! I can confirm this fixes the issue we found:

root@ubuntu:/# apt-cache policy efivar
efivar:
  Installed: 37-2ubuntu2
  Candidate: 37-2ubuntu2
  Version table:
 *** 37-2ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status
root@ubuntu:/# efibootmgr -v
Timeout: 0 seconds
BootOrder: 0000
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)

Bug Watch Updater (bug-watch-updater)
Changed in efivar (Debian):
status: Unknown → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in efivar (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.