Shimx64 does not know how to interact with unsecured efi bios

Bug #1809529 reported by Bougron
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Invalid
Undecided
Unassigned
shim (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hello.

Shimx64 does not know how to interact with unsecured efi bios!

some EFI computers have not developed the secure layer.
Shimx64 is always installed but its installation does not work.

This installation is planting.
When ubuntu is started by other methods, reinstalling the shimx64 package continues to crash!

This second installation is also planting.
It is then impossible to make the command "apt upgrade" which asks to make the command "dpkg --configure -a" to correct the problem because this last command also crashes!!!

I ask you to ask the user his opinion before installing shimx64 in the nvram!
If he says NO, do not install shimx64 in the nvram since grubx64 is enough for unsafe EFI bios....

 See a French discussion https://forum.ubuntu-fr.org/viewtopic.php?id=2034753

 See a French discussion https://forum.ubuntu-fr.org/viewtopic.php?id=2034636

 See a French discussion https://forum.ubuntu-fr.org/viewtopic.php?id=2034753

Thanks.

description: updated
description: updated
Revision history for this message
Ryan Harper (raharper) wrote :

Hello,

I added the shim package to this bug as it appears that your issue is related to the shim rather than curtin. If you believe that curtin is related to your issue, please provide additional details about how curtin is involved in your scenario.

Changed in curtin:
status: New → Invalid
Revision history for this message
Steve Langasek (vorlon) wrote :

The title of this bug is certainly false. shimx64.efi consistently works on EFI systems with or without SecureBoot enabled.

I clicked on the first forum thread that you linked to, but it is a long discussion and doesn't enlighten me as to what the actual problem is that you're experiencing or why you are blaming shim for it. Please provide the complete output of the commands that are failing on your system.

Changed in shim (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for shim (Ubuntu) because there has been no activity for 60 days.]

Changed in shim (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.