On Tue, 14 May 2019, Steven Haigh wrote:
The final fix would be figuring out why pygrub currently boots the
*second*
entry in the resulting grub.cfg - unlike how F29 worked. This may be either a
fix on the grub2-mkconfig or pygrub side - I'm not quite sure yet. This would
likely restore functionality completely. At least until something else more
suitable is done?
The answer to why is easy. pygrub just ignores "if" instructions and there
is a
set default=1
line in an if clause from /etc/grub.d/08_fallback_counting so it
defaults to the second entry as they are numbered from 0.
Michael Young