I have also verified package grub2-common 2.14-2ubuntu2.1 from resolute- proposed fixes the issues I was seeing (comment above) on a clean minimal installation.
Testing: Using the same reboot test I used originally (comment above), I verified the issue was present _prior_ to installing grub2-common 2.14-2ubuntu2.1. I then installed grub2-common 2.14-2ubuntu2.1 and verified the After dependency was corrected: user@tmp-ubs26tst2:~$ systemctl cat grub-initrd-fallback.service # /usr/lib/systemd/system/grub-initrd-fallback.service [Unit] Description=GRUB failed boot detection After=local-fs.target After=grub2-common.service After=sleep.target ConditionPathExists=/boot/grub/grub.cfg [Service] Type=oneshot ExecStart=/usr/bin/grub-editenv /boot/grub/grubenv unset initrdfail ExecStart=/usr/bin/grub-editenv /boot/grub/grubenv unset prev_entry TimeoutSec=0 [Install] WantedBy=multi-user.target rescue.target emergency.target sleep.target user@tmp-ubs26tst2:~$ Next, I confirmed the grub2 recovery menu issues were resolved with the new package. In regular use over the last day or so I have not noticed any other issues with grub on this test system. Thank you for promoting this fixed package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2156423 Title: Fix grub-initrd-fallback.service order To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2156423/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
