package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[shubham mishra]

I was installing xUbuntu LTS and it crashed while trying to install grub2.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
Uname: Linux 4.9.8-040908-lowlatency x86_64
NonfreeKernelModules: rtsx_usb_sdmmc rtsx_usb amdkfd amd_iommu_v2 amdgpu i915 ttm i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 drm mii ahci libahci wmi video fjes
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootEFIContents:
 fw
 fwupx64.efi
Date: Sat Dec 16 14:09:43 2017
Df:
 Filesystem 1K-blocks Used Available Use% Mounted on
 /dev/sda5 355534780 324287240 13164368 97% /
 /dev/sdb 1212416 1212416 0 100% /cdrom
 udev 4029676 0 4029676 0% /dev
 tmpfs 808892 9484 799408 2% /run
EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: efibootmgr: EFI variables are not supported on this system.
EFITables:

ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 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)]

The attached dpkg log shows that grub was successfully installed on your system in EFI mode. But your bug report claims that your system is not booted in EFI mode, and shows that you are booted into an upstream 'lowlatency' kernel version, not the 4.4.0 kernel that was installed as part of the Xubuntu installation; and that this lowlatency kernel was present on your disk at the time that the install was done, which means you did not reformat the partition that was mounted at /boot as part of the install; and your /boot/efi is also reported to be empty.

This is not an actionable bug report given the currently available information. You will need to explain precisely what steps you took that led you to this situation in order for us to determine if there is a bug in Ubuntu.

[shubham mishra (smishr4)]

Hi Steve,

Thank you for your response, yes you are right that I was not doing a fresh installation, instead I was overwriting the existing Ubuntu 14.04 installed on my system, keeping apps and documents and settings as it is, that means, not erasing the previously installed Operating System.

I think part of the problem was my BIOS settings which had boot type set to UEFI instead of Legacy, I later changed it to Legacy and it successfully installed xUbuntu 16.04 in the second attempt.

Although I did not lose any documents and settings but because of the unsuccessful first attempt I lost my apps, which I had to reinstall after my system got ready :o(

If BIOS settings is the problem then installation should halt at the very beginning and compel the user to correct it, instead of going ahead with it and exit with an error leaving an unclean installation and loss of user apps.

Shubham Mishra

[Steve Langasek (vorlon)]

> If BIOS settings is the problem then installation should halt at the
> very beginning and compel the user to correct it, instead of going ahead
> with it and exit with an error leaving an unclean installation and loss
> of user apps.

100% agreed, but since we haven't ever reproduced such failures ourselves,
it's difficult to know what we should be detecting.

Even now, it's difficult to know what part of your bug report came from the
actual failed install or not. It definitely doesn't tell us what failed, or
why.

Could you please tar up /var/log/apt/term.log and /var/log/installer from
this system and attach it to the bug?

[Launchpad Janitor (janitor)]

[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.]