package shim-signed 1.35+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1: cannot find EFI directory.

Your bug report shows that this is an upgrade of the shim-signed package. How/why do you have the shim-signed package installed, if your system is not booted in UEFI mode (according to the output of efibootmgr) and you do not have an EFI system partition mounted at /boot/efi?

Hi Steve,

I really don't know.

I did a clean install of xubuntu 18.10 (for testing purposes) on an
existing partition on a laptop which also has 18.04 on another partition.
That 18.10 installation ended with an error at the very end (ubiquity
complained about not being able to install grub 2). Ubiquity seems to have
decided that it was installing on a uefi-machine.

Ever since then every update complains about shim-signed and
 grub-efi-amd64-signed.

You'll find more bugs reported by me about shim and grub-efi.

I'm just an end user, I did not knowingly do anything to install shim or
grub-efi. Don't know what they are, really.

Is there anything more I can provide to help?

Op vr 1 jun. 2018 21:30 schreef Steve Langasek <<email address hidden>
>:

> Your bug report shows that this is an upgrade of the shim-signed
> package. How/why do you have the shim-signed package installed, if your
> system is not booted in UEFI mode (according to the output of
> efibootmgr) and you do not have an EFI system partition mounted at
> /boot/efi?
>
> ** Changed in: shim-signed (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774646
>
> Title:
> package shim-signed 1.35+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:
> Testing Xubuntu 18.10.
>
> Is there any more information I can/should provide?
>
> ProblemType: Package
> DistroRelease: Ubuntu 18.10
> Package: shim-signed 1.35+13-0ubuntu2
> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
> Uname: Linux 4.15.0-22-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or
> directory: '/proc/sys/kernel/moksbstate_disabled'
> ApportVersion: 2.20.10-0ubuntu3
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Fri Jun 1 15:34:57 2018
> DpkgHistoryLog:
> Start-Date: 2018-06-01 15:34:55
> Commandline: apt upgrade
> Requested-By: willem (1000)
> Upgrade: networkd-dispatcher:amd64 (1.7-0ubuntu4, 1.7-0ubuntu5),
> publicsuffix:amd64 (20180328.1055-1, 20180523.2326-2), libpsl5:amd64
> (0.20.1-1, 0.20.2-1), liborc-0.4-0:amd64 (1:0.4.28-1, 1:0.4.28-2),
> gir1.2-snapd-1:amd64 (1.39-0ubuntu1, 1.41-0ubuntu1), shim-signed:amd64
> (1.34.9+13-0ubuntu2, 1.35+13-0ubuntu2), libsnapd-glib1:amd64
> (1.39-0ubuntu1, 1.41-0ubuntu1)
> EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2:
> EFI variables are not supported on this system.
> EFITables:
>
> ErrorMessage: installed shim-signed package post-installation script
> subprocess returned error exit status 1
> Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-3
> PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal,
> 2.7.15~rc1-1
> RelatedPackageVersions:
> dpkg 1.19.0.5ubuntu3
> apt 1.7.0~alpha0ubuntu1
> SourcePackage: shim-signed
> Title: package shim-signed 1.35+13-0ubuntu2 failed to install/upgrade:...

> Ubiquity seems to have decided that it was installing on a uefi-machine.

And it was almost certainly correct, but the installation of the UEFI bootloader failed because your disk did not have an EFI System Partition to install to. Your 18.10 install was only bootable afterwards because you previously had BIOS GRUB installed to your MBR.

So, did I do something wrong when I installed 18.10?

And is there anything else I can provide to help?

Op vr 1 jun. 2018 22:25 schreef Steve Langasek <<email address hidden>
>:

> > Ubiquity seems to have decided that it was installing on a uefi-
> machine.
>
> And it was almost certainly correct, but the installation of the UEFI
> bootloader failed because your disk did not have an EFI System Partition
> to install to. Your 18.10 install was only bootable afterwards because
> you previously had BIOS GRUB installed to your MBR.
>
> ** Changed in: shim-signed (Ubuntu)
> Status: Incomplete => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774646
>
> Title:
> package shim-signed 1.35+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:
> Triaged
>
> Bug description:
> Testing Xubuntu 18.10.
>
> Is there any more information I can/should provide?
>
> ProblemType: Package
> DistroRelease: Ubuntu 18.10
> Package: shim-signed 1.35+13-0ubuntu2
> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
> Uname: Linux 4.15.0-22-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or
> directory: '/proc/sys/kernel/moksbstate_disabled'
> ApportVersion: 2.20.10-0ubuntu3
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Fri Jun 1 15:34:57 2018
> DpkgHistoryLog:
> Start-Date: 2018-06-01 15:34:55
> Commandline: apt upgrade
> Requested-By: willem (1000)
> Upgrade: networkd-dispatcher:amd64 (1.7-0ubuntu4, 1.7-0ubuntu5),
> publicsuffix:amd64 (20180328.1055-1, 20180523.2326-2), libpsl5:amd64
> (0.20.1-1, 0.20.2-1), liborc-0.4-0:amd64 (1:0.4.28-1, 1:0.4.28-2),
> gir1.2-snapd-1:amd64 (1.39-0ubuntu1, 1.41-0ubuntu1), shim-signed:amd64
> (1.34.9+13-0ubuntu2, 1.35+13-0ubuntu2), libsnapd-glib1:amd64
> (1.39-0ubuntu1, 1.41-0ubuntu1)
> EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2:
> EFI variables are not supported on this system.
> EFITables:
>
> ErrorMessage: installed shim-signed package post-installation script
> subprocess returned error exit status 1
> Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal,
> 3.6.5-3
> PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal,
> 2.7.15~rc1-1
> RelatedPackageVersions:
> dpkg 1.19.0.5ubuntu3
> apt 1.7.0~alpha0ubuntu1
> SourcePackage: shim-signed
> Title: package shim-signed 1.35+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 install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1774646/+subscriptions
>

On Sat, Jun 02, 2018 at 04:16:45AM -0000, Willem Hobers wrote:
> So, did I do something wrong when I installed 18.10?

No, this is a known bug in ubiquity which is targeted for fixing in 18.04.1.