[Bug 1232237] Re: GRUB_CRYPTODISK_ENABLE should be GRUB_ENABLE_CRYPTODISK

[Launchpad Bug Tracker]

This bug was fixed in the package grub2 - 2.02~beta2-5

---------------
grub2 (2.02~beta2-5) experimental; urgency=medium


  * Add a number of EFI debugging commands to the signed image (lsefi,
    lsefimmap, lsefisystab, lssal).
  * Add gfxterm_background to the signed image so that background_image
    works in UEFI Secure Boot mode.  Thanks to syscon-hh for the report.

 -- Colin Watson <cjwatson at debian.org>  Mon, 27 Jan 2014 10:03:00 +0000

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

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

Title:
  GRUB_CRYPTODISK_ENABLE should be GRUB_ENABLE_CRYPTODISK

Status in “grub2” package in Ubuntu:
  Fix Released

Bug description:
  There's a bug in the grub source package for encrypted disk support
  where the shell environment variable is incorrectly named as
  "GRUB_CRYPTODISK_ENABLE" when it should be "GRUB_ENABLE_CRYPTODISK".
  This prevents grub-install from correctly building an encrypted
  installation.

  $ grep -rn GRUB_CRYPTODISK_ENABLE {/usr/share/grub/*,/usr/sbin/grub-install}
  /usr/share/grub/grub-mkconfig_lib:74:  if [ x$GRUB_CRYPTODISK_ENABLE = xy ]; then
  /usr/share/grub/grub-mkconfig_lib:167:  if [ x$GRUB_CRYPTODISK_ENABLE = xy ]; then
  /usr/sbin/grub-install:707:    if [ x$GRUB_CRYPTODISK_ENABLE = xy ]; then

  An in-place workaround is:

  $ sudo sed -i 's/GRUB_CRYPTODISK_ENABLE/GRUB_ENABLE_CRYPTODISK/g'
  {/usr/share/grub/grub-mkconfig_lib,/usr/sbin/grub-install}

  Upstream now has a patch which does the same thing. See:

  http://lists.gnu.org/archive/html/grub-devel/2013-09/msg00147.html

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