[Bug 1460521] Re: UEFI BootOrder is not empty after I removed the last boot entry.

[Mathieu Trudel-Lapierre]

Looks like efibootmgr would need further commits to land before
301c0628. I'm not especially comfortable with backporting an update to
use libefivar as well. In that light, looks like the BootOrder change is
a better idea.

Shih-Yuan, have you tested the fix you're proposing? My main concern is
that although having an empty BootOrder is good when there are no
devices to boot from, if you reboot the system like this it might
trigger the firmware to do recovery steps, and revert changes made. It
would be better to just ensure that the deduplication code is correct.

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

Title:
  UEFI BootOrder is not empty after I removed the last boot entry.

Status in HWE Next Project:
  Triaged
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efibootmgr source package in Trusty:
  Triaged

Bug description:
  There is no such issue in Ubuntu 14.10 or 15.04.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:	Ubuntu
  Description:	Ubuntu 14.04.2 LTS
  Release:	14.04
  Codename:	trusty

  $ dpkg-query -W efibootmgr 
  efibootmgr	0.5.4-7ubuntu1.1

  $ sudo efibootmgr -v || echo "*failed*"
  BootCurrent: 0000
  Timeout: 0 seconds
  BootOrder: 0000
  Boot0000* ubuntu	HD(1,800,100000,b8d7d8e9-4ac4-46cc-8bd0-8d90d6df1df4)File(\EFI\ubuntu\shimx64.efi)

  $ sudo efibootmgr -v -B -b 0 || echo "*failed*"
  *failed*

  $ sudo efibootmgr -v || echo "*failed*"
  BootCurrent: 0000
  Timeout: 0 seconds
  BootOrder: 0000

  $ sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi || echo "*failed*"
  BootCurrent: 0000
  Timeout: 0 seconds
  BootOrder: 0000,0000
  Boot0000* ubuntu	HD(1,800,100000,b8d7d8e9-4ac4-46cc-8bd0-8d90d6df1df4)File(\EFI\ubuntu\shimx64.efi)

  You can see BootOrder having the duplicate 0000.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1460521/+subscriptions