(Ubuntu-GNOME, debconf passthrough) package shim-signed 1.17~15.10.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Smot]

Installing updates - it failed during the installation of shim-signed

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: shim-signed 1.17~15.10.1+0.8-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-41.48-generic 4.2.8-ckt11
Uname: Linux 4.2.0-41-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
BootEFIContents:
 grub.cfg
 grubx64.efi
 MokManager.efi
 shimx64.efi
Date: Thu Jul 21 20:35:42 2016
DuplicateSignature: package:shim-signed:1.17~15.10.1+0.8-0ubuntu2:subprocess installed post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit status 128
InstallationDate: Installed on 2015-04-08 (470 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150406)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt 1.0.10.2ubuntu3
SourcePackage: shim-signed
Title: package shim-signed 1.17~15.10.1+0.8-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

[Steve Langasek (vorlon)]

The error in your logs is:

quit

Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, <GEN0> line 11.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, <GEN0> line 11.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 11.
Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212, <GEN0> line 11.
Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, <GEN0> line 11.
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, <GEN0> line 11.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, <GEN0> line 11.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 11.
Use of uninitialized value $val in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 83, <GEN2> line 8.
Use of uninitialized value $val in concatenation (.) or string at /usr/share/perl5/Debconf/Format/822.pm line 84, <GEN2> line 8.

This looks like the install "hung" from your perspective, but the debconf interface was waiting from input somewhere; and it never got it, possibly because of a ^C in the terminal.

What package manager frontend were you using for this upgrade? The apport-attached information doesn't show this, but only shows that aptdaemon was used as the backend.

[Smot (smot-msn)]

I think your suggestion is correct. I used dpkg-reconfigure to re-run
shim-signed and a window popped up asking me to disable secure boot.
This didn't appear in the original run.

I'm using Ubuntu Gnome 15.10 (updated to 16.04 today), and used the
Software Updater app to apply updates. This was the original Ubuntu
updater, rather than the new one that now ships with 16.04.

I guess this report can now be closed.

Thanks for your help.

On 21/07/16 21:13, Steve Langasek wrote:
> The error in your logs is:
>
> quit
>
> Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, <GEN0> line 11.
> Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, <GEN0> line 11.
> Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 11.
> Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212, <GEN0> line 11.
> Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, <GEN0> line 11.
> Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, <GEN0> line 11.
> Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, <GEN0> line 11.
> Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 11.
> Use of uninitialized value $val in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 83, <GEN2> line 8.
> Use of uninitialized value $val in concatenation (.) or string at /usr/share/perl5/Debconf/Format/822.pm line 84, <GEN2> line 8.
>
> This looks like the install "hung" from your perspective, but the
> debconf interface was waiting from input somewhere; and it never got it,
> possibly because of a ^C in the terminal.
>
> What package manager frontend were you using for this upgrade? The
> apport-attached information doesn't show this, but only shows that
> aptdaemon was used as the backend.
>
> ** Changed in: shim-signed (Ubuntu)
> Status: New => Incomplete
>

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Olivier (arteau-olivier)]

I had the same issue on Ubuntu 16.04 when updating with the Software Updater.

[Olivier (arteau-olivier)]

I was able to finish the installation by running "dpkg --configure -a" in the Terminal. The "shim-signed" package required some terminal interaction to correctly finish. The issue might be that some application like Software Updater don't interact well with the install script.