Comment # 16 on bug 1185441 from Gary Ching-Pang Lin

(In reply to Tiago Marques from comment #15)
> (In reply to Gary Ching-Pang Lin from comment #13)
> > (In reply to Tiago Marques from comment #12)
> > > Hi,
> > > 
> > > I've been hit by this for some months now. Every Grub2 update, I get the
> > > same message as OP.
> > > Not sure which grub package is to blame and I'm using EFI and secure boot.
> > > 
> > > I've managed to (twice) solve the issue by booting a live USB, chrooting and
> > > then running 'shim-install'.
> > > 
> > > Not sure where the bug is or if this helps. I'm available to test other
> > > things out to help fix this.
> > 
> > Before upgrading "shim", could you try "mokutil --enable-validation" and
> > reboot the system to clean up MokSBState?
> 
> Tried but the command is asking me for a password. I have no password set on
> the BIOS. Is this the expected behavior?

That's a password used to verify physical access when modifying MokSBState
variable. During the next boot, MokManager will ask if you want to "Change
Secure Boot state" and randomly ask 3 characters of the password you set. It's
an one-time password and will be dropped after use.