package shim-signed 1.51.3+15.7-0ubuntu1 failed to install/upgrade: проблемы зависимостей — оставляем триггеры не обработанными

Bug #2037711 reported by Igor Golov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

grub-efi-bin package installation failed with code 10

Ubuntu:
Description: Ubuntu 22.04.3 LTS
Release: 22.04

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: shim-signed 1.51.3+15.7-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Нет такого файла или каталога: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootEFIContents:
 BOOTX64.CSV
 grub.cfg
 grubx64.efi
 mmx64.efi
 shimx64.efi
CasperMD5CheckResult: pass
Date: Fri Sep 29 13:04:24 2023
EFIBootMgr:
 BootCurrent: 0001
 Timeout: 1 seconds
 BootOrder: 0001,0000
 Boot0000* Windows Boot Manager VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...i................
 Boot0001* ubuntu HD(1,GPT,c36a52c7-daba-437c-97f5-680b4f483397,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
ErrorMessage: проблемы зависимостей — оставляем триггеры не обработанными
GrubDiff: Двоичные файлы /boot/efi/EFI/ubuntu/grubx64.efi и /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed различаются
InstallationDate: Installed on 2023-01-15 (256 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04
PythonDetails: /usr/bin/python3.11, Python 3.11.5, python-is-python3, 3.9.2-2
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt 2.4.10
SecureBoot: 6 0 0 0 0
SourcePackage: shim-signed
Title: package shim-signed 1.51.3+15.7-0ubuntu1 failed to install/upgrade: проблемы зависимостей — оставляем триггеры не обработанными
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Igor Golov (igor-golov) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Exit code 10 is an error from debconf. This means that the grub-efi-amd64-signed package needed to prompt you to ask a question about the configuration before proceeding, but there was an error while asking.

Were you shown a dialog during the upgrade, perhaps one asking you which device the bootloader needed to be installed to? Did you dismiss this dialog?

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

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

Changed in grub2-signed (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.