package grub-efi-amd64-signed 1.93.5+2.02-2ubuntu8.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

Bug #1790994 reported by Albert Young
172
This bug affects 37 people
Affects Status Importance Assigned to Milestone
grub2-signed (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I just tried to update

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64-signed 1.93.5+2.02-2ubuntu8.4
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_42
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Sep 5 21:01:50 2018
ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2016-05-05 (853 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3ubuntu0.1
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.93.5+2.02-2ubuntu8.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-03 (125 days ago)

Revision history for this message
Albert Young (youngac3) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2-signed (Ubuntu):
status: New → Confirmed
Revision history for this message
Rishi (tricksumo) wrote :

I am also facing same issue.

Revision history for this message
maurice1952 (therese-diana) wrote :

Après démarrage de l'ordinateur une fenêtre apparait : "problème logiciel détecté" heureusement ceci n'empêche pas l,ordinateur de fonctionner correctement. J'espère qu'avec ubuntu 18/10 ce bug va disparaitre.
Google translation : After starting the computer a window appears: "problem detected software" fortunately this does not prevent the computer from working properly. I hope that with ubuntu 18/10 this bug will disappear.

Revision history for this message
Ying (selkie-upsilon) wrote :

Some more information when trying to fix this.

sudo dpkg --configure -a
Setting up grub-efi-amd64-signed (1.93.5+2.02-2ubuntu8.4) ...
Installing for x86_64-efi platform.
Could not prepare Boot variable: No space left on device
grub-install: error: efibootmgr failed to register the boot entry: Input/output error.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of shim-signed:
 shim-signed depends on grub-efi-amd64-signed; however:
  Package grub-efi-amd64-signed is not configured yet.

dpkg: error processing package shim-signed (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 grub-efi-amd64-signed
 shim-signed

But /boot has space.
df -h | grep boot
/dev/sda1 511M 4.7M 507M 1% /boot/efi

Looking at similar problems (https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1776271) could need a BIOS update. Currently

sudo lshw | less
  *-core
       description: Motherboard
       product: 2B47
       vendor: HP
       physical id: 0
       version: 1.04
     *-firmware
          description: BIOS
          vendor: AMI
          physical id: 0
          version: A0.13
          date: 12/21/2015
          size: 64KiB
          capacity: 8128KiB

Have not yet rebooted after the upgrade, but in case reboot fails, I will report back on a different computer.

Revision history for this message
Ying (selkie-upsilon) wrote :

Update: I fixed my problem by updating the BIOS.

System: HP PAVILION 550-257NG

I was running BIOS version A0.13 and updated to version A0.20. After reboot, I ran
sudo dpkg --configure -a

Setting up grub-efi-amd64-signed (1.93.5+2.02-2ubuntu8.4) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
Setting up shim-signed (1.34.9.2+13-0ubuntu2) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.

Incidentally, for those on this particular (or similar) HP desktops, the BIOS download executable can unfortunately only be run on Windows (due to the use of an HP proprietary SoftPAQ download/extraction manager obscuring the BIOS .bin file needed), so either use your Windows partition or use a different Windows computer. After the "press any key to continue the SoftPAQ update process" command prompt screen, do press any key -- don't worry, it won't flash your other system, it would check the SSID and realize that you are not using the HP computer, then offer the possibility to create a recovery USB for applying the update to your system using the UFEI recovery options on boot.

HP-specific instructions: https://support.hp.com/us-en/product/hp-pavilion-550-200-desktop-pc-series/9259612/model/10683933/document/c00007682
Refer to "Update the BIOS when Windows do not start" if you do not have a Windows partition.
Step 6 in the instruction on creating a USB stick only appeared after I pressed a key on the "continue the SoftPAQ update process" command prompt screen.

Revision history for this message
Steve Langasek (vorlon) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1805490, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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.