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
Bugs, which is subscribed to 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1614675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
