Sigh... good going microsloth for violating the uefi spec already. I see two possibilities:
1) The machine is using the default bootloader because for some reason, ubuntu failed to update the efi boot catlog to point to grub. 2) The machine's buggy firmware assumes that if the default loader exists, it should use that, no matter what the boot catalog says. If you can run efibootmgr -v on an affected machine, this could show which theory is correct. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366546 Title: Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1366546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
