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

[Shih-Yuan Lee]

In fact, I have tried https://github.com/rhinstaller/efibootmgr/commit/301c0628f7fa7333791d2b5d79eb8e02fc848ee7 and it doesn't work for this issue.
I think my fix is the right way to fix this problem so I also made a pull request at https://github.com/rhinstaller/efibootmgr/pull/32 about this.
I have used this patch for some Ubuntu OEM projects and it does work well.

BTW, efibootmgr code base is very different between Ubuntu 14.04, 14.10 and 15.04.
Although Ubuntu 14.10 and 15.04 don't have the duplicate issue, but it still has other issue by the same script in comment #1.
We just didn't see any side effect from that issue yet.

-- 
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