[Bug 722950] Re: ctrl-x does not work in grub-efi

[dann frazier]

@Aapo - has this ever worked for you - e.g. in a previous Ubuntu
release? If not, I'd suggest filing a new issue. This bug has been
verified to fix an issue for some users, and maybe unrelated to what you
are seeing.

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

Title:
  ctrl-x does not work in grub-efi

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  New
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in grub2 source package in Zesty:
  Won't Fix
Status in grub2-signed source package in Zesty:
  Won't Fix
Status in grub2 source package in Artful:
  Fix Released
Status in grub2-signed source package in Artful:
  Fix Released

Bug description:
  [Impact]
  On some UEFI platforms, useful key combinations fail to work over the serial console. In particular, ^x/F10 - one of which is needed to boot after interactively editing the boot menu. This leaves end users without a sane way to tweak command line arguments, and potentially other system recovery tasks.

  [Test Case]
  Boot such a UEFI system to the GRUB menu. Press 'e' to edit the commandline, then attempt to continue the boot using "^x".

  [Regression Risk]
  The proposed fix is a cherry-pick from upstream that we've been shipping in Ubuntu since 17.10 w/o any any known regressions. However, it is possible that such regressions exist - e.g. if a platform's firmware has a buggy implementation fo the EFI_SIMPLE_TEXT_INPUT_EX protocol.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/722950/+subscriptions