(Ubuntu 17.04, non-UEFI) package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thanks for reporting. This appears to be an install made with an Ubuntu 17.04 desktop image, is that correct?

Yes, it was. I have since been able to successfully install it but not as
an upgrade or a boot option.

On Apr 17, 2017 4:26 PM, "Steve Langasek" <email address hidden>
wrote:

> Thanks for reporting. This appears to be an install made with an Ubuntu
> 17.04 desktop image, is that correct?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683332
>
> Title:
> package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to
> install/upgrade: subprocess installed post-installation script
> returned error exit status 1
>
> Status in shim-signed package in Ubuntu:
> New
>
> Bug description:
> Installation error
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
> Uname: Linux 4.10.0-19-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: 0
> .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
> .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c'
> ApportVersion: 2.20.4-0ubuntu4
> AptOrdering:
> shim:amd64: Install
> shim-signed:amd64: Install
> NULL: ConfigurePending
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Thu Apr 13 17:35:08 2017
> Df:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 106519624 19167484 81918184 19% /
> /dev/sdb1 31309792 7250544 24059248 24% /cdrom
> udev 8150832 0 8150832 0% /dev
> tmpfs 1633464 17744 1615720 2% /run
> EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2:
> EFI variables are not supported on this system.
> ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> RelatedPackageVersions:
> dpkg 1.18.10ubuntu2
> apt 1.4
> SourcePackage: shim-signed
> Title: package shim-signed 1.28+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)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+
> bug/1683332/+subscriptions
>

You say you have successfully installed the shim-signed package? Were you trying to manually install it, or do you recall any information from the system installer that explained why it was being installed on your system?

When I tried to manually install it I got an error (same as above) on that
file and an efi signed file as well. Im not sure why it wanted to load it.
My guess is maybe because I initially wanted to preserve data going from
raring to 17.4? When I tried a reinstallation, forcing UEFI but telling it
to erase and install, I got no errors.

On Apr 17, 2017 6:50 PM, "Steve Langasek" <email address hidden>
wrote:

> You say you have successfully installed the shim-signed package? Were
> you trying to manually install it, or do you recall any information from
> the system installer that explained why it was being installed on your
> system?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683332
>
> Title:
> package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to
> install/upgrade: subprocess installed post-installation script
> returned error exit status 1
>
> Status in shim-signed package in Ubuntu:
> New
>
> Bug description:
> Installation error
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
> Uname: Linux 4.10.0-19-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: 0
> .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
> .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c'
> ApportVersion: 2.20.4-0ubuntu4
> AptOrdering:
> shim:amd64: Install
> shim-signed:amd64: Install
> NULL: ConfigurePending
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Thu Apr 13 17:35:08 2017
> Df:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 106519624 19167484 81918184 19% /
> /dev/sdb1 31309792 7250544 24059248 24% /cdrom
> udev 8150832 0 8150832 0% /dev
> tmpfs 1633464 17744 1615720 2% /run
> EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2:
> EFI variables are not supported on this system.
> ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> RelatedPackageVersions:
> dpkg 1.18.10ubuntu2
> apt 1.4
> SourcePackage: shim-signed
> Title: package shim-signed 1.28+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)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+
> bug/1683332/+subscriptions
>

On Mon, Apr 17, 2017 at 11:29:37PM -0000, Cindy wrote:
> When I tried to manually install it I got an error (same as above) on that
> file and an efi signed file as well. Im not sure why it wanted to load it.
> My guess is maybe because I initially wanted to preserve data going from
> raring to 17.4? When I tried a reinstallation, forcing UEFI but telling it
> to erase and install, I got no errors.

When you say "forcing UEFI", what does that mean? I'm not aware of any
option in the Ubuntu installer that allows forcing of UEFI installation.

I think it was referring to a bios option I have on my system for booting
capabilities between different partitions. It's a Zotac.

On Apr 17, 2017 9:20 PM, "Steve Langasek" <email address hidden>
wrote:

> On Mon, Apr 17, 2017 at 11:29:37PM -0000, Cindy wrote:
> > When I tried to manually install it I got an error (same as above) on
> that
> > file and an efi signed file as well. Im not sure why it wanted to load
> it.
> > My guess is maybe because I initially wanted to preserve data going from
> > raring to 17.4? When I tried a reinstallation, forcing UEFI but telling
> it
> > to erase and install, I got no errors.
>
> When you say "forcing UEFI", what does that mean? I'm not aware of any
> option in the Ubuntu installer that allows forcing of UEFI installation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683332
>
> Title:
> package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to
> install/upgrade: subprocess installed post-installation script
> returned error exit status 1
>
> Status in shim-signed package in Ubuntu:
> New
>
> Bug description:
> Installation error
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
> Uname: Linux 4.10.0-19-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: 0
> .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
> .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c'
> ApportVersion: 2.20.4-0ubuntu4
> AptOrdering:
> shim:amd64: Install
> shim-signed:amd64: Install
> NULL: ConfigurePending
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Thu Apr 13 17:35:08 2017
> Df:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 106519624 19167484 81918184 19% /
> /dev/sdb1 31309792 7250544 24059248 24% /cdrom
> udev 8150832 0 8150832 0% /dev
> tmpfs 1633464 17744 1615720 2% /run
> EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2:
> EFI variables are not supported on this system.
> ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> RelatedPackageVersions:
> dpkg 1.18.10ubuntu2
> apt 1.4
> SourcePackage: shim-signed
> Title: package shim-signed 1.28+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)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+
> bug/1683332/+subscriptions
>

If the system boots in EFI mode, it will have a different behavior than if it's booted in other BIOS modes: in EFI, you would see a text-based menu, with a black background when booting from the install CD (or USB). If you're not booting the installer in EFI mode, you would see a graphical menu with the Ubuntu logo.

When you did the install, do you recall what happened when you booted to the installer (assuming Ubuntu was installed recently)?

I had tried it both ways. It wasn't until I told the installer to erase and
install that I had no issues. I used efi on that install attempt.

On Apr 18, 2017 8:31 AM, "Mathieu Trudel-Lapierre" <email address hidden>
wrote:

> If the system boots in EFI mode, it will have a different behavior than
> if it's booted in other BIOS modes: in EFI, you would see a text-based
> menu, with a black background when booting from the install CD (or USB).
> If you're not booting the installer in EFI mode, you would see a
> graphical menu with the Ubuntu logo.
>
> When you did the install, do you recall what happened when you booted to
> the installer (assuming Ubuntu was installed recently)?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683332
>
> Title:
> package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to
> install/upgrade: subprocess installed post-installation script
> returned error exit status 1
>
> Status in shim-signed package in Ubuntu:
> New
>
> Bug description:
> Installation error
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
> Uname: Linux 4.10.0-19-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: 0
> .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
> .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c'
> ApportVersion: 2.20.4-0ubuntu4
> AptOrdering:
> shim:amd64: Install
> shim-signed:amd64: Install
> NULL: ConfigurePending
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Thu Apr 13 17:35:08 2017
> Df:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 106519624 19167484 81918184 19% /
> /dev/sdb1 31309792 7250544 24059248 24% /cdrom
> udev 8150832 0 8150832 0% /dev
> tmpfs 1633464 17744 1615720 2% /run
> EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2:
> EFI variables are not supported on this system.
> ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> RelatedPackageVersions:
> dpkg 1.18.10ubuntu2
> apt 1.4
> SourcePackage: shim-signed
> Title: package shim-signed 1.28+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)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+
> bug/1683332/+subscriptions
>

Could be that I was forcing UEFI while still trying to keep the data from
the previous installation that caused the anomaly?

On Apr 18, 2017 8:31 AM, "Mathieu Trudel-Lapierre" <email address hidden>
wrote:

> If the system boots in EFI mode, it will have a different behavior than
> if it's booted in other BIOS modes: in EFI, you would see a text-based
> menu, with a black background when booting from the install CD (or USB).
> If you're not booting the installer in EFI mode, you would see a
> graphical menu with the Ubuntu logo.
>
> When you did the install, do you recall what happened when you booted to
> the installer (assuming Ubuntu was installed recently)?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1683332
>
> Title:
> package shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1 failed to
> install/upgrade: subprocess installed post-installation script
> returned error exit status 1
>
> Status in shim-signed package in Ubuntu:
> New
>
> Bug description:
> Installation error
>
> ProblemType: Package
> DistroRelease: Ubuntu 17.04
> Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
> Uname: Linux 4.10.0-19-generic x86_64
> .proc.sys.kernel.moksbstate_disabled: 0
> .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23'
> .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c:
> Error: [Errno 2] No such file or directory: '/sys/firmware/efi/efivars/
> SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c'
> ApportVersion: 2.20.4-0ubuntu4
> AptOrdering:
> shim:amd64: Install
> shim-signed:amd64: Install
> NULL: ConfigurePending
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Thu Apr 13 17:35:08 2017
> Df:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda1 106519624 19167484 81918184 19% /
> /dev/sdb1 31309792 7250544 24059248 24% /cdrom
> udev 8150832 0 8150832 0% /dev
> tmpfs 1633464 17744 1615720 2% /run
> EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2:
> EFI variables are not supported on this system.
> ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> RelatedPackageVersions:
> dpkg 1.18.10ubuntu2
> apt 1.4
> SourcePackage: shim-signed
> Title: package shim-signed 1.28+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)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+
> bug/1683332/+subscriptions
>