[Bug 1184297] Re: Secure boot failed, claiming boot is against security policy

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 2.15.10

---------------
ubiquity (2.15.10) saucy; urgency=low

  [ Kaj Ailomaa ]
  * Change Ubuntu Studio background in ubiquity-dm.

  [ Jeremy Bicha ]
  * Don't tell automake to install everything to ubiquity-frontend-gtk and
    try to clean up after
  * Reorganize app icon handling
    - Fixes missing app icon in GNOME Shell (LP: #1164573)
    - Use improved icon from Humanity as fallback icon
  * Update *.install files for above changes
  * Fix minor lintian warning by not installing empty /usr/share/applications/

  [ Aurélien Gâteau ]
  * KDE: Set icon theme to Oxygen, shows icons on standalone Ubiquity

  [ Dan Chapman ]
  * Add initial autopilot support! UI testing, brave new world!

  [ Stéphane Graber ]
  * Install the shim and signed grub and kernels by default on all UEFI
    machines instead of relying on the SecureBoot nvram variable.
    (LP: #1184297)
  * Automatic update of included source packages: bterm-unifont 1.3,
    grub-installer 1.78ubuntu8, partconf 1.42, partman-basicmethods 54,
    partman-jfs 40, partman-reiserfs 55, partman-xfs 52.
  * Fix mix tabs/spaces in test_ubiquity_custom.py.
  * Fix autopkgtests not passing pyflakes.
 -- Stephane Graber <stgraber at ubuntu.com>   Thu, 18 Jul 2013 18:10:17 -0400

** Changed in: ubiquity (Ubuntu)
       Status: In Progress => Fix Released

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

Title:
  Secure boot failed, claiming boot is against security policy

Status in “grub-installer” package in Ubuntu:
  Fix Released
Status in “grub2” package in Ubuntu:
  Fix Released
Status in “grub2-signed” package in Ubuntu:
  Fix Released
Status in “ubiquity” package in Ubuntu:
  Fix Released
Status in “grub-installer” source package in Precise:
  Triaged
Status in “grub2” source package in Precise:
  Triaged
Status in “grub2-signed” source package in Precise:
  Triaged
Status in “ubiquity” source package in Precise:
  Triaged

Bug description:
  I've struggled to install Linux on a Packard Bell EasyNote LV11HC,
  without having to accept the Windows 8 license, and my progress is
  documented in http://www.linlap.com/packard_bell_easynote_lv .  Had to
  pull the hard drive and install to a USB stick to be able to get into
  the firmware menu and enable the F12 boot menu. After finally being
  able to install Ubuntu 13.04 on the hard drive, the UEFI firmware
  refused to boot the hard drive, claiming it was against the security
  policy.  I was able to boot Ubuntu by powering on again and using F12
  to pick the hard drive.

  No idea what is wrong, but can help with debugging the next few days
  before I switch to legacy BIOS and put it into production.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: shim 0~20120906.bcd0a4e8-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 26 11:14:38 2013
  Dependencies:
   
  InstallationDate: Installed on 2013-05-26 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: shim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1184297/+subscriptions