This bug was fixed in the package shim-signed - 1.37~18.04.2
---
shim-signed (1.37~18.04.2) bionic; urgency=medium
* debian/control: add Breaks: grub-efi-amd64-signed (<< 1.93.7), as the new
version of shim exercises a bug in relocation code for chainload that was
fixed in
This SRU has been rolled back due to functional regressions that have
been reported when chainloading from shim 15 to shim 13 in MAAS.
Investigation is ongoing.
** Changed in: shim-signed (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
You received this bug notification because
This bug was fixed in the package shim-signed - 1.34.9.1
---
shim-signed (1.34.9.1) bionic; urgency=medium
* update-secureboot-policy: fix quoting for key/again password handling to
mokutil. (LP: #1770579)
* update-secureboot-policy: don't allow backtracking at the "main"
Verification-done on bionic with shim-signed/1.34.9.1:
I checked that you can no longer backtrack in the GNOME debconf frontend
from the "enable secure boot" question to cause the dialog to fail.
Backtracking is no longer accepted, only allowed as part of the password
handling steps.
** Tags
Hello Bruno, or anyone else affected,
Accepted shim-signed into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/shim-
signed/1.34.9.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
- Any user of Secure Boot with DKMS modules having the GNOME debconf frontend
enabled or other debconf frontends that are not Dialog or readline.
+ Users of SecureBoot with DKMS modules can trigger a maintainer script crash
by using the buttons presented in
** Description changed:
+ [Impact]
+ Any user of Secure Boot with DKMS modules having the GNOME debconf frontend
enabled or other debconf frontends that are not Dialog or readline.
+
+ [Test case]
+ 1) Delete /var/lib/shim-signed/mok/MOK.* if exists.
+ 2) Run 'sudo update-secureboot-policy
This bug was fixed in the package shim-signed - 1.35
---
shim-signed (1.35) cosmic; urgency=medium
* update-secureboot-policy: fix quoting for key/again password handling to
mokutil. (LP: #1770579)
* update-secureboot-policy: don't allow backtracking at the "main" question
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/shim/+git/shim-signed/+merge/347167
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767091
Title:
package shim-signed
** Tags added: id-5af997fc3ad8c3a41ba1538e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767091
Title:
package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
installed shim-signed
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767091
Title:
package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
Thank you for reporting this issue.
The shim-signed package, on upgrade, needs to prompt you in order to
make changes to the MokManager configuration in your firmware. These
prompts are done over debconf. 'exit status 30' is an indicator that
something has failed in the debconf.
Looking at the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shim-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767091
Title:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767091
Title:
package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade:
installed shim-signed package
14 matches
Mail list logo
