(In reply to Andrei Borzenkov from comment #19) > This bug report is becoming rather messy. > > The problem you reported is fixed. The problem you discuss now does not > appear to be related to Leap bootloader, because you have problems with > manually created boot entries, and Leap bootloader is not involved in any > way. I leave it to Michael, but I tend to think this bug should be closed as > resolved. How is it fixed? A 'simple' upgrade of a running 13.2 server -> Leap renders the system unbootable. Without a patch, as yet unverified, uncomitted, grub2-mkconfig will not execute.