[Bug 1687201] [NEW] Secure Boot Does not allow Ubuntu to boot even after creating ESP partition from ubuntu and erasing everything else
Nitin
mailer.nitin at gmail.com
Sat Apr 29 14:40:22 UTC 2017
Public bug reported:
This is a Acer system with UEFI and Secure Boot option
Installed the latest firmware and also installed all TPM modules from the vendor.
Freshly installed Ubuntu 16.04.02 by choosing 'Erase everything and install Ubuntu' installation and update went fine but when re booted the system No Bootable Media error was thrown.
Though system is working by installing a binary key using Mokmanager.efi
but don't know why this step was needed also the system crashes if there
is any update.
Cheers
-Nitin
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: shim 0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr 29 20:02:26 2017
Dependencies:
InstallationDate: Installed on 2017-04-23 (6 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
SourcePackage: shim
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: shim (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim in Ubuntu.
https://bugs.launchpad.net/bugs/1687201
Title:
Secure Boot Does not allow Ubuntu to boot even after creating ESP
partition from ubuntu and erasing everything else
Status in shim package in Ubuntu:
New
Bug description:
This is a Acer system with UEFI and Secure Boot option
Installed the latest firmware and also installed all TPM modules from the vendor.
Freshly installed Ubuntu 16.04.02 by choosing 'Erase everything and install Ubuntu' installation and update went fine but when re booted the system No Bootable Media error was thrown.
Though system is working by installing a binary key using
Mokmanager.efi but don't know why this step was needed also the system
crashes if there is any update.
Cheers
-Nitin
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: shim 0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr 29 20:02:26 2017
Dependencies:
InstallationDate: Installed on 2017-04-23 (6 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
SourcePackage: shim
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1687201/+subscriptions
More information about the foundations-bugs
mailing list