*** This bug is a duplicate of bug 1891680 ***
https://bugs.launchpad.net/bugs/1891680
A number of upgrade issues were addressed in grub2 2.04-1ubuntu26.4 in
20.04, which was released back in September. I am going to mark this as
a duplicate of bug #1891680.
However, where the grub debconf state on a system is /wrong/, it is not
possible to guard against this failure on reboot because the running
system cannot know which disk, which is not listed in the debconf state,
has the out-of-date first-stage bootloader.
If you are running an official Ubuntu image in Azure, it should
definitely be in a state that the debconf values are NOT wrong. Please
open a separate bug report for this and drop a reference to that bug
here.
** This bug has been marked a duplicate of bug 1891680
grub-pc needs to detect when debconf points to invalid drive and stop in
preinst, before unpacking files, and also treat this as a failure in postinst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
'grub_file_filters' not found."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
