[Bug 1614675] Re: package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: the postinst ran /usr/sbin/update-secureboot-policy which kept forking off itself, then exiting, repeat forever until I killed it
Steve Langasek
steve.langasek at canonical.com
Tue Aug 23 20:49:00 UTC 2016
What did you see here that makes you think update-secureboot-policy was
forking and exiting?
The output shows that your debconf interface was in an inconsistent
state:
Setting up shim-signed (1.18~14.04.1+0.8-0ubuntu2) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212, <GEN0> line 23.
Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, <GEN0> line 23.
Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, <GEN0> line 23.
[...]
So this looks like it's the same as bug #1603642.
** Changed in: shim-signed (Ubuntu)
Status: New => Incomplete
** Summary changed:
- package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: the postinst ran /usr/sbin/update-secureboot-policy which kept forking off itself, then exiting, repeat forever until I killed it
+ (trusty, debconf passthrough) package shim-signed 1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: the postinst ran /usr/sbin/update-secureboot-policy which kept forking off itself, then exiting, repeat forever until I killed it
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shim-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1614675
Title:
(trusty, debconf passthrough) package shim-signed
1.18~14.04.1+0.8-0ubuntu2 failed to install/upgrade: the postinst ran
/usr/sbin/update-secureboot-policy which kept forking off itself, then
exiting, repeat forever until I killed it
Status in shim-signed package in Ubuntu:
Incomplete
Bug description:
From what I could tell, /usr/sbin/update-secureboot-policy either kept
invoking itself from the original, or it was forking and exiting.
Either way, I left it for 10 minutes, but it never finished. I killed
it.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: shim-signed 1.18~14.04.1+0.8-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
Uname: Linux 3.13.0-93-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
BootEFIContents:
grub.cfg
grubx64.efi
MokManager.efi
shimx64.efi
Date: Thu Aug 18 12:13:57 2016
DuplicateSignature: package:shim-signed:1.18~14.04.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 2014-07-22 (758 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
dpkg 1.17.5ubuntu5.7
apt 1.0.1ubuntu2.14
SourcePackage: shim-signed
Title: package shim-signed 1.18~14.04.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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1614675/+subscriptions
More information about the foundations-bugs
mailing list