This bug was fixed in the package shim-signed - 1.37~18.04.3
---
shim-signed (1.37~18.04.3) bionic; urgency=medium
* Don't fail non-interactive upgrade of nvidia module and module removals
(LP: #1726803)
-- Balint Reczey Thu, 25 Oct 2018 20:55:38 +0200
** Changed in:
For the record the shim-signed fix alone is enough to fix the reported
issue, i.e. installation failing when the nvidia module changes dirs.
The u-u fix is an attempt to fix the generic case, when an update brings
in a new dkms module, but this is not happening in the archive at the
moment and is
Verified with shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1:
...
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo rm
/var/lib/shim-signed/mok/MOK.der
ubuntu@autopkgtest:/var/cache/apt/archives$ sudo update-secureboot-policy
--new-key
Generating a new Secure Boot signing key:
Hello Patrick, 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.37~18.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Description changed:
[Impact]
* When Secure Boot is enabled and MOK is not set and a new dkms module
is installed sim-signed asks for a Secure Boot MOK, or aborts package
installation in non-interactive mode. When unattended-upgrades performed
the upgrade the aborted installation
** Merge proposal linked:
https://code.launchpad.net/~rbalint/shim/+git/shim-signed/+merge/357843
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
This bug was fixed in the package shim-signed - 1.38
---
shim-signed (1.38) cosmic; urgency=medium
* Don't fail non-interactive upgrade of nvidia module and module removals
(LP: #1726803)
-- Balint Reczey Thu, 11 Oct 2018 18:12:37 +0200
** Changed in: shim-signed (Ubuntu)
** Description changed:
[Impact]
- * When Secure Boot is enabled and a new dkms module is installed sim-
- signed asks for a new Secure Boot key, or aborts package installation in
- non-interactive mode. When unattended-upgrades performed the upgrade the
- aborted installation leaves an
** Changed in: shim-signed (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
Title:
** Changed in: shim-signed (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
Title:
unattended-upgrades +
** Merge proposal linked:
https://code.launchpad.net/~rbalint/shim/+git/shim-signed/+merge/356440
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
@vorlon My bad, thought that a generic solution would be useful in u-u,
but now I'm implementing now the special case.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Balint, I wrote in comment #4 that changing the nvidia stack is expected
on upgrades, and that we should special-case this in shim-signed to
suppress the error. Why are you proposing to change unattended-upgrades
instead?
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status: New =>
** Description changed:
- [Impact] (WIP)
+ [Impact]
- * An explanation of the effects of the bug on users and
+ * When Secure Boot is enabled and a new dkms module is installed sim-
+ signed asks for a new Secure Boot key, or aborts package installation in
+ non-interactive mode. When
14 matches
Mail list logo
