[Bug 1600224] Re: shim-signed updates break self signed UEFI systems
xzqjack
xzqjack at hotmail.com
Tue Jul 19 06:37:03 UTC 2016
Hi, i'm a newer to Ubuntu.I want to tell you about my experience about
some mistake of shim-signed package and my way to figure out it.
Yesterday, some mistake about shim-signed occurred.The updater of Ubuntu
got stuck and turned black. I have to force closing updater.But when i
reboot the computer, i couldn't enter the Ubuntu graphical interfaces.
When i input password and press login , scree flashed and ask for
passward again. However, the "tty1" (press Ctrl+Alt+F1) worked fine.
Then i remove shim-signed and reinstall it.The install process ask me
to disable UEFI secure boot. I choose No on first time and yes on second
time. But both didn't work.
Finally, i entered BIOS and turn the secure boot item into "other
operation system " from "Windows UEFI". And it workd fine.
I completely have no idea about that. I wish my experience could provide
something useful to help improve shim-signed.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1600224
Title:
shim-signed updates break self signed UEFI systems
Status in shim-signed package in Ubuntu:
New
Bug description:
Updating shim-signed on a self signed UEFI platform without Microsoft
keys is rendered unbootable. An example is a QEMU instance that is
self signed.
Isn't there a way to notify the platform owner that they should resign
their UEFI utilities before rebooting ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1600224/+subscriptions
More information about the foundations-bugs
mailing list