group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <722950@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package grub2 - 2.02~beta2-36ubuntu3.16

---------------
grub2 (2.02~beta2-36ubuntu3.16) xenial; urgency=medium

  [ dann frazier ]
  * Use EFI_SIMPLE_TEXT_INPUT_EX to support key combinations.
    (LP: #722950)

  [ Mathieu Trudel-Lapierre ]
  * util/grub-install.c: Use MokManager EFI binary name without
    the .signed extension now that shim handles signing via sbsigntool
    natively. (LP: #1708245)
    - debian/patches/install_signed.patch
  * debian/control: Breaks shim << 13 due to the renamed MokManager binary.

 -- dann frazier <dannf@xxxxxxxxxx>  Wed, 10 Jan 2018 17:04:34 -0700

** Changed in: grub2 (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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