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

[Steve Langasek]

Hello Shih-Yuan, or anyone else affected,

Accepted efibootmgr into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/efibootmgr/0.5.4-7ubuntu1.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: efibootmgr (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
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:
  Fix Committed

Bug description:
  [Impact]
  Trusty users who attempt to reorganize EFI boot entries aggressively (deleting everything and creating a new Ubuntu entry, or deleting everything and leaving the installer create a new entry) may run into issues when a new BootOrder entry is created with an empty list: they will find a duplicate entry for the one added.

  Upon the last deletion, users may also find that the command reports
  failure when the BootOrder entry was deleted successfully.

  [Test case]
  - Run the provided test_efi.sh on a system booted in EFI mode (that has EFI support). This test is destructive, only run it on a system if you know what you are doing and are able to recreate the appropriate Boot entries for starting the system.

  This is runnable also on qemu, provided one uses the UEFI OVMF BIOS:
  0) sudo apt install ovmf
  1) qemu-img create -f qcow2 disks/efi-testdisk1.qcow2 32g
  2) qemu-system-x86_64 -name efi-test-x86_64 -enable-kvm -monitor stdio -serial pty -boot menu=on -m 1024 -m 1024 -bios /usr/share/qemu/OVMF.fd -net user -net nic -drive file=trusty-desktop-amd64.iso,media=cdrom -drive file=disks/efi-testdisk1.qcow2

  [Regression Potential]
  A failure case following the application of this fix may be that BootOrder entries remain after deletion of a Boot entry when it should have been removed from the list. BIOSes should successfully recover from this if there are other valid BootOrder entries to boot from, but may fail to do so.

  ----

  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