Could not delete variable: Interrupted system call (package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1)

The error in your log is:
Setting up shim-signed (1.34.9+13-0ubuntu2) ...
Installing for x86_64-efi platform.
Could not delete variable: Interrupted system call
grub-install: error: efibootmgr failed to register the boot entry: Block device required.
dpkg: error processing package shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned error exit status 1

It appears that there is a problem with your firmware that prevents shim from uploading the bootloader configuration variables. Is it possible that you are affected by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 ?

Hi Steve,

yes, it is possible
after installing ubuntu 17.04 i could not anymore to use the cdrom or usb
port for booting from there..
the laptop is a lenovo b50-10..

2018-04-30 6:43 GMT+02:00 Steve Langasek <email address hidden>:

> The error in your log is:
> Setting up shim-signed (1.34.9+13-0ubuntu2) ...
> Installing for x86_64-efi platform.
> Could not delete variable: Interrupted system call
> grub-install: error: efibootmgr failed to register the boot entry: Block
> device required.
> dpkg: error processing package shim-signed (--configure):
> installed shim-signed package post-installation script subprocess
> returned error exit status 1
>
> It appears that there is a problem with your firmware that prevents shim
> from uploading the bootloader configuration variables. Is it possible
> that you are affected by
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 ?
>
> ** Changed in: shim-signed (Ubuntu)
> Status: New => Incomplete
>
> ** Summary changed:
>
> - package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
> installed shim-signed package post-installation script subprocess returned
> error exit status 1
> + Could not delete variable: Interrupted system call (package shim-signed
> 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package
> post-installation script subprocess returned error exit status 1)
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1767881).
> https://bugs.launchpad.net/bugs/1767761
>
> Title:
> Could not delete variable: Interrupted system call (package shim-
> signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-
> signed package post-installation script subprocess returned error exit
> status 1)
>
> Status in shim-signed package in Ubuntu:
> Incomplete
>
> Bug description:
> This prevents my system from fully upgrading.
>
> ProblemType: Package
> DistroRelease: Ubuntu 18.04
> Package: shim-signed 1.34.9+13-0ubuntu2
> ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
> Uname: Linux 4.15.0-15-generic x86_64
> NonfreeKernelModules: wl nvidia_modeset nvidia
> .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or
> directory: '/proc/sys/kernel/moksbstate_disabled'
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> Date: Sun Apr 29 10:16:56 2018
> ErrorMessage: installed shim-signed package post-installation script
> subprocess returned error exit status 1
> InstallationDate: Installed on 2015-09-02 (970 days ago)
> InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-3
> 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.1
> SecureBoot: 6 0 0 0 0
> SourcePackage: shim-signed
> Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
> installed shim-signed package post-installation script subprocess returned
> error exit status 1
> UpgradeStatus: No upgrade log present (probably fresh ins...

Hi Gustavo, thanks for following up. If you are affected by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 please look at the information there about using a custom kernel to recover your firmware's writable state.

For the record, you mention having problems after installing Ubuntu 17.04, but this bug only affected systems which were running Ubuntu 17.10. But the symptoms you're describing certainly sound like this bug, so I would guess that you just have mentioned the wrong version number.

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1767276, so 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.