Hi,
Has there been any progress towards fixing this? Looking at the changelogs, I
haven't seen anything mentioning the current ticket, nor any update for some
time. Just trying to see if I can update my shim installation without breaking
my machine again.
Thanks in advance,
Paul.
Dear Maintainer,
I can also confirm the bug with shim 1.38 right after it was published and
installed. I have opened another bug that seems very similar: #999746. It
might therefore be a duplicate -- sorry if it is.
Regards,
Paul.
I can also confirm this bug with shim 1.38.
Dear Maintainer,
I confirm this issue. After upgrade to Debian 10.10 (including a new
version shim-signed), Secure Boot no longer works.
I proceeded as usual :
- I added my key via command
# mokutil --import my-key.der
- I rebooted
- I obtained shim screen to propose enroll my k
Dear Maintainer,
I can confirm this issue - after upgrade on 21.06.2021, Secure Boot no
longer works. Signing the third party kernel modules reports no
problems, but the signed modules are not loaded on boot. Issue appears
to be that the MOK isnot available during and/or after boot.
host:/# mokut
Package: shim* (shim-signed, shim-signed-common,
shim-helpers-amd64-signed, shim-unsigned)
Version: 1.36~1
Platform: amd64
Dear Maintainer,
I'm using Secure Boot for an AMD64 system and I have installed the
non-free nvidia graphics driver (nvidia-driver). To use Secure Boot, I
6 matches
Mail list logo
