system doesn't boot after patch w/ bug 1925010

[Nik F]

Ubuntu doesn't boot on my system after the patch yesterday which includes the fix for this bug: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010

Not sure if it's directly related to that bug, or something else. Is there some sort of boot logging I can enable? Or have my system stop rebooting itself in a loop, and just display errors?

Ubuntu also reset my grub config, which has been filed as a bug multiple times, yet never fixed. It would be really great if Ubuntu stopped doing that.

Ubuntu 21.04, up to date as of yesterday. I'll have to dig for more information later.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1928455/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Steve Langasek (vorlon)]

You say the system is rebooting in a loop? What is shown on the screen when it does this?

[Steve Langasek (vorlon)]

Just to confirm, when you say it doesn't boot after the patch yesterday: this means you had 21.04 installed, and the system did boot with 15.4-0ubuntu1, but now does not boot with 15.4-0ubuntu2?

[Steve Langasek (vorlon)]

Can you tell us what hardware this is happening on?

It would be helpful for diagnosing this if you would:

- boot the system from external media (an Ubuntu install image)
- run 'apport-collect 1928455' to send us relevant information about your system
- run 'sudo mokutil --set-verbosity true' to put shim into verbose mode
- reboot and try to capture any messages that appear on the screen

[Nik F (chef-niko)]

Today my system booted up fine, though I'm not sure what would cause the change in behaviour.

According to dpkg log, these are the packages updated yesterday:
2021-05-14 07:01:00 status installed distro-info:amd64 1.0
2021-05-14 07:01:03 status installed ubuntu-advantage-tools:amd64 27.0.2~21.04.1
2021-05-14 07:01:07 status installed man-db:amd64 2.9.4-2

It seems I was a bit too quick to file this bug. I apologize for my over-zealousness.

I certainly do appreciate the information about how to put shim in to verbose mode, and I will be sure to do that if I have boot problems in the future, as well as collect more info from the live media.

Interestingly, my system seems to be running much better without having to pass in the iommu related options I usually do. That's great to see!

[Steve Langasek (vorlon)]

Thanks for following up. We can't be too cautious when it comes to boot regressions, especially when we're changing a critical component like shim. So your bug report is appreciated, even if it turned out to be nothing.