[Bug 1693968] [NEW] double free error when secure boot is enabled

Seth Forshee seth.forshee+lp at canonical.com
Sat May 27 03:26:59 UTC 2017


Public bug reported:

I just did an upgrade and rebooted, and upon loading the kernel grub
presented me with a "double free" error. It was doing this no matter
what kernel I tried to boot, including kernels which were booting fine
before. Out of desperation I disabled secure boot in the bios and the
kernel loaded and booted without error. When I turned secure boot back
on the error came back.

It's likely that none of kernels I have installed have a valid
signature, since I generally install test builds before uploading
kernels, so maybe that's related.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: grub-efi-amd64 2.02~beta3-4ubuntu4
ProcVersionSignature: Ubuntu 4.11.0-5.10-generic 4.11.3
Uname: Linux 4.11.0-5-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri May 26 22:19:01 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-03-30 (58 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: Upgraded to artful on 2017-04-27 (29 days ago)

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  double free error when secure boot is enabled

Status in grub2 package in Ubuntu:
  New

Bug description:
  I just did an upgrade and rebooted, and upon loading the kernel grub
  presented me with a "double free" error. It was doing this no matter
  what kernel I tried to boot, including kernels which were booting fine
  before. Out of desperation I disabled secure boot in the bios and the
  kernel loaded and booted without error. When I turned secure boot back
  on the error came back.

  It's likely that none of kernels I have installed have a valid
  signature, since I generally install test builds before uploading
  kernels, so maybe that's related.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: grub-efi-amd64 2.02~beta3-4ubuntu4
  ProcVersionSignature: Ubuntu 4.11.0-5.10-generic 4.11.3
  Uname: Linux 4.11.0-5-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May 26 22:19:01 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-30 (58 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: grub2
  UpgradeStatus: Upgraded to artful on 2017-04-27 (29 days ago)

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



More information about the foundations-bugs mailing list