package shim-signed 1.37~18.04.11+15.4-0ubuntu9 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| grub2-signed (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Error message at startup
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.37~18.
ProcVersionSign
Uname: Linux 4.15.0-200-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.28
AptOrdering:
firefox:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Fri Jan 6 10:00:10 2023
DpkgHistoryLog:
Start-Date: 2023-01-06 10:00:05
Commandline: /usr/bin/
Upgrade: firefox:amd64 (108.0+
EFIBootMgr:
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000
Boot0000* ubuntu HD(1,GPT,
ErrorMessage: problemi con le dipendenze - lasciato non configurato
InstallationDate: Installed on 2018-08-29 (1590 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Missing: /boot/efi/
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageV
dpkg 1.19.0.5ubuntu2.4
apt 1.6.14
SourcePackage: shim-signed
Title: package shim-signed 1.37~18.
UpgradeStatus: No upgrade log present (probably fresh install)

The error in your log is:
Configurazione di grub-efi- amd64-signed (1.173. 2~18.04. 1+2.04- 1ubuntu47. 4)... amd64-signed (--configure): amd64-signed script post-installation ha restituito lo stato di errore 1
Installazione per la piattaforma x86_64-efi.
grub-install: errore: impossibile trovare la directory EFI.
dpkg: errore nell'elaborare il pacchetto grub-efi-
il sottoprocesso installato pacchetto grub-efi-
There is no EFI System Partition mounted according to the`df` output in your report. Did you manually repartition your system and remove it?
Your report indicates that you are running on a system that is using UEFI firmware, so the EFI System Partition is required, and grub and shim need to be able to find it to update boot assets. So this is a configuration error of some kind, likely not a bug in the package.