This bug was fixed in the package shim-signed - 1.17
---------------
shim-signed (1.17) yakkety; urgency=medium
* update-secureboot-policy: rework setting capabilities to stop having
the backup capability while showing an error message; which won't affect
the Dialog debconf frontend but otherwise made the GTK frontend confusing.
* update-secureboot-policy: all debconf prompts should be at priority
critical: there is no good default to pick, we must prompt the user.
* debian/templates: make the password inputs be standard inputs; this is an
unfortunate workaround to aptdaemon not having access to the debconf
password database on desktop; since the frontend runs as an unprivileged
user. See bug LP#1599981 (LP: #1599051)
-- Mathieu Trudel-Lapierre <[email protected]> Thu, 07 Jul 2016
16:58:45 -0400
** Changed in: shim-signed (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599051
Title:
package shim-signed 1.16~14.04.1+0.8-0ubuntu2 failed to
install/upgrade: subprocess installed post-installation script was
killed by signal (Terminated)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1599051/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
