package shim-signed 1.37~18.04.2+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

Bug #1798956 reported by Jan Johansson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
shim-signed (Ubuntu)
New
Undecided
Unassigned

Bug Description

Won't boot automatically after upgrade, but if i press F12 i can select ubuntu or harddrive in the F12 boot menu to boot on.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.37~18.04.2+15+1533136590.3beb971-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Filen eller katalogen finns inte: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Sat Oct 20 13:29:44 2018
EFITables:
 okt 20 13:39:34 janne-LIFEBOOK-NH532 kernel: efi: EFI v2.31 by American Megatrends
 okt 20 13:39:34 janne-LIFEBOOK-NH532 kernel: efi: ACPI=0xca7d3000 ACPI 2.0=0xca7d3000 SMBIOS=0xf0690 MPS=0xfcd00
 okt 20 13:39:34 janne-LIFEBOOK-NH532 kernel: secureboot: Secure boot could not be determined (mode 0)
 okt 20 13:39:41 janne-LIFEBOOK-NH532 fwupd[1691]: disabling plugin because: failed to startup uefi: UEFI firmware updating not supported
ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2018-09-25 (24 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3ubuntu0.1
SecureBoot: 22 0 0 0 0
SourcePackage: shim-signed
Title: package shim-signed 1.37~18.04.2+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jan Johansson (janne-l) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

The error in your logs is:

Setting up shim-signed (1.37~18.04.2+15+1533136590.3beb971-0ubuntu1) ...
Installerar för x86_64-efi-plattformar.
grub-install: fel: efibootmgr failed to register the boot entry: Okänt fel -1.
dpkg: error processing package shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned error exit status 1

The output of efibootmgr also shows that the boot order configured in your firmware does not list Ubuntu first - which is why the system does not automatically boot to Ubuntu.

But Ubuntu would not have caused itself to not be listed first, so something outside of Ubuntu must have done this. And if Ubuntu is not able to write to the variables in firmware - for unclear reasons - then this is not fixable by Ubuntu.

Do you have firmware security settings in place that are preventing Ubuntu from updating the BootOrder?

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.