Comment 16 for bug 1799767

frank (franknfurter) wrote :

Oh my god, that is really a strange behavin. As you said, I entered that mokutil command and rebooted the system, entered BIOS. I enabled CSM, saved the config and rebooted. In the attachment you see the message from shim after BIOS splash screen. But what happened then?
Suddenly I saw the grub menu and after 10 secs ubuntu starts automagically in secure boot mode. I didn't believe that. Thought I had made a mistake. So I switched off verbosity and rebooted. But, and that's surprising, I did not saw any grub menu, just the black screen as before.
So I had to boot into BIOS, set CSM to "auto" and reboot. And I did it again, just to verify this. I switched verbosity on, rebooted, enabled CSM, rebooted again and I have seen the grub menu. Ubuntu starts automagically in secure boot mode.

Conclusion:
CSM enabled and mokutil verbosity true-> grub menu and SecureBoot
CSM enabled and mokutil verbosity false-> Black screen

Further info: Yesterday I run an update that has been listed in update manager. Here you see the apt history:
Start-Date: 2018-11-02 21:20:21
Commandline: aptdaemon role='role-commit-packages' sender=':1.73'
Upgrade: libparted2:amd64 (3.2-20, 3.2-20ubuntu0.1), libparted-fs-resize0:amd64 (3.2-20, 3.2-20ubuntu0.1), parted:amd64 (3.2-20, 3.2-20ubuntu0.1), mokutil:amd64 (0.3.0-0ubuntu5, 0.3.0+1538710437.fb6250f-0ubuntu2~18.04.1), secureboot-db:amd64 (1.1, 1.4~ubuntu0.18.04.1)
End-Date: 2018-11-02 21:20:29

So what about updates at the moment. Is it ok for you if I still run these updates or should I wait with this. You know, I always want to install security patches.