@space_agent: Agreed, it is sad . . . and key point on the bug is that at the top line for "assigned" it shows "unassigned" . . . very interesting considering the large number of people who have posted on this bug report over . . . quite a long awhile.
It does seem like some folks have figured out a "work around" . . . none of them seemed to apply to my investigation of their suggestions . . . I'm still waiting for the devs to be "assigned" to the situation . . . and get a real fix in the tubes on it. But, the great joy of linux is that there are "other options" to choose from . . . many of them. In the case of ubuntu it appears that the vision statement is "ubuntu first" . . . or only, they figure that most users only will use one OS, and so after an install it will only boot into ubuntu. But for multi-boot users such as myself that approach is problematic. Just last week I ran an apt on one of my ubuntu installs and once again upgrading grub in that process wiped my grub menu . . . so the problem still continues . . . . I had to once again boot the SuperGrub2 disk . . . find the "vmlinuz" for my Tumbleweed install and then run their "os-prober" to get my grub menu back . . . . I've been with ubuntu flavors for many years, but this problem has diminished my enthusiasm . . . because "they don't recognize it as a viable issue . . ." . . . to even "assign" it . . . . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863434 Title: 20.04 grub menu not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1863434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
