(Ubuntu-Mate 16.10, non-UEFI system) package shim-signed 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[bk dubey]

1.
Ubuntu Mate 16.10

2.
shim-signed:
  Installed: 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3
  Candidate: 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3
  Version table:
 *** 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3 500
        500 http://in.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
        100 /var/lib/dpkg/status

3.
I was expecting that it is not going to boot at all because i got an error during the installation, which interrupted the installation, and then pc rebooted.

4.
I Was installing "ubuntu mate 16.10" when this happened [Note that i already have Kubuntu 16.04.1 and ubuntu mate 16.04.1 installed on other separate partitions.]. I was following the standard installation process i.e. selected language (en-US), Keyboard layout (US), checked download updates during installation, and install third party software.
    I believe the "install third party software" option led me to "turn off secure boot" option, which i did by giving it a random password, which led me to an error during installation. Then, the pc rebooted.
    After this i booted into kubuntu (since i didnt see any ubuntu mate 16.10 in grub menu), and updated the grub then booted into ubuntu mate 16.10 which led me to this error.

Other Information that might be useful:-
Setting up shim-signed (1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package shim-signed (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up grub-efi-amd64-signed (1.74+2.02~beta2-36ubuntu11) ...
grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 subprocess installed post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: shim-signed 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 shim:amd64: Install
 shim-signed:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
BootEFIContents:
 fw
 fwupx64.efi
Date: Mon Oct 24 15:12:31 2016
EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system.
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.1
SourcePackage: shim-signed
Title: package shim-signed 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Steve Langasek (vorlon)]

Your bug report shows:

EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system.

And also:

Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.
dpkg: error processing package shim-signed (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up grub-efi-amd64-signed (1.74+2.02~beta2-36ubuntu11) ...
grub-install: error: /usr/lib/grub/i386-pc/modinfo.sh doesn't exist. Please specify --target or --directory.
dpkg: error processing package grub-efi-amd64-signed (--configure):
 subprocess installed post-installation script returned error exit status 1

It appears to be an error that something is trying to install shim-signed on your system.

Mathieu, is there anything in the ubiquity code that would be /requesting/ installation of shim-signed?

[Mathieu Trudel-Lapierre (cyphermox)]

No, everything is gated on what archdetect reports, and thus only shows iff we're running on an EFI system.

That said, I wonder if something might be not properly following the ignore_uefi debconf template.

When you ran the installer, did you get a message window about other OS being installed and whether to continue in UEFI mode?

If you tried to start the live CD again on that machine, could you get us the output of the following commands, before you run the installer at all?

ls -lR /sys/firmware/efi
archdetect

The output of archdetect should probably read "amd64/efi". If it's the case, archdetect thinks it's on an EFI system, and following the install steps should lead to installing shim. Any issues there would have to do with an incomplete implementation of EFI (and that's why I'd like to know what is in /sys/firmware/efi)

If it reads "amd64/generic", then we have a bigger problem, where somehow shim is installed where it really shouldn't be.

[bk dubey (bkd1)]

Thank you for the replies.
Q1. When you ran the installer, did you get a message window about other OS
being installed and whether to continue in UEFI mode?
YES.

Q2. If you tried to start the live CD again on that machine, could you get
us the output of the following commands, before you run the installer at
all?
NO. My apologies but I can't.
        Because at that time i was running the said machine in "CSM mode"
and every distro is getting installed in that mode (including 16.04.1
mentioned previously). But after getting the error with UMATE 16.10 , i
changed few things. I formated 1st partition, created an ESP partition,
disabled "CSM mode" and re-installed UMATE 16.10 (without any errors). That
is why i replied this late.

The output of "archdetect" says *amd64/efi* . Does this value changes? (I
mean is it logical or does it represent something physical).
I am using brand new built (hope it helps):- ASUS Pro Gaming Z170, i5
6600K, Corsair Vengeance LPX 4 GB DDR4 2400Mhz etc..

One last thing, the UMATE 16.04.1 (on other partition) used to give an
error at boot time but after creating ESP partition and disabling CSM mode
from UEFI it stopped. I dont remember it exactly but it read something like
this:- "drmi915 gem init stolen with stolen memory region some hexadecimal
addresses".

On Wed, Oct 26, 2016 at 7:51 PM Mathieu Trudel-Lapierre <
<email address hidden>> wrote:

> No, everything is gated on what archdetect reports, and thus only shows
> iff we're running on an EFI system.
>
> That said, I wonder if something might be not properly following the
> ignore_uefi debconf template.
>
> When you ran the installer, did you get a message window about other OS
> being installed and whether to continue in UEFI mode?
>
> If you tried to start the live CD again on that machine, could you get
> us the output of the following commands, before you run the installer at
> all?
>
> ls -lR /sys/firmware/efi
> archdetect
>
> The output of archdetect should probably read "amd64/efi". If it's the
> case, archdetect thinks it's on an EFI system, and following the install
> steps should lead to installing shim. Any issues there would have to do
> with an incomplete implementation of EFI (and that's why I'd like to
> know what is in /sys/firmware/efi)
>
> If it reads "amd64/generic", then we have a bigger problem, where
> somehow shim is installed where it really shouldn't be.
>
>
> ** 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/1636148
>
> Title:
> package shim-signed 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3
> failed to install/upgrade: subprocess installed post-installation
> script returned error exit status 1
>
> Status in shim-signed package in Ubuntu:
> Incomplete
>
> Bug description:
>
> 1.
> Ubuntu Mate 16.10
>
> 2.
> shim-signed:
> Installed: 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3
> Candidate: 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3
> Version table:
> *** 1.21.3+0.9+1465500757.14a5905.is.0.8-0ubuntu3 500
> 500 http://in.archive.ubuntu.co...

[Mathieu Trudel-Lapierre (cyphermox)]

I don't expect the value to change if the firmware configuration doesn't, but if CSM is enabled, then it *might* not report amd64/efi; and the fact that you disabled CSM since then changes the behavior of the firmware. *However*, this gives me something to look into some more; it's possible CSM on that firmware (I think I tested this combination on Lenovo firmware, but not others) doesn't expose all the EFI variables needed.