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

[Aapo Rantalainen]

Ctrl+x not working in grub editing mode with ubuntu-18.04(-alpha). 
grub2-common:
  Installed: 2.02-2ubuntu7

grub-efi-amd64-signed:
  Installed: 1.92+2.02-2ubuntu7

Might relate platform, device is: MacBookPro14,3

These works:
Ctrl+a = home
Ctrl+e = end
Ctrl+c = command line

(At least) These are not working with ctrl: o,n,p,i,u,f,b,h,k,l


I try patch to ctrl+a to start boot.

--- grub2-2.02.orig/grub-core/normal/menu_entry.c
+++ grub2-2.02/grub-core/normal/menu_entry.c
@@ -1346,6 +1347,8 @@ grub_menu_entry_run (grub_menu_entry_t e
 
 	case GRUB_TERM_CTRL | 'a':
 	case GRUB_TERM_KEY_HOME:
-	  if (! beginning_of_line (screen, 1))
-	    goto fail;
-	  break;
+	  run (screen);
+	  goto refresh;

But still ctrl+a acts like home-key.


Also in grub-menu (grub-core/normal/menu.c) only ctrl+a, ctrl+e and ctrl+c are working. 
Ctrl+p and ctrl+n (up/down) are not working.

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